- 11 Oct, 2011 9 commits
-
-
Greg Kroah-Hartman authored
Used the correct dev_warn() call instead. Cc: K. Y. Srinivasan <kys@microsoft.com> Signed-off-by:Greg Kroah-Hartman <gregkh@suse.de>
-
Greg Kroah-Hartman authored
These aren't used by anyone anymore, so remove them before someone tries to use them again. Cc: K. Y. Srinivasan <kys@microsoft.com> Signed-off-by: -
Greg Kroah-Hartman authored
It's a global symbol, so properly prefix it and use the proper EXPORT value as well. Cc: K. Y. Srinivasan <kys@microsoft.com> Signed-off-by: -
Greg Kroah-Hartman authored
No one outside of the hyperv core needs to include the asm/hyperv.h file, so don't put it in the "global" include/linux/hyperv.h file. Cc: K. Y. Srinivasan <kys@microsoft.com> Signed-off-by: -
Greg Kroah-Hartman authored
After many years wandering the desert, it is finally time for the Microsoft HyperV code to move out of the staging directory. Or at least the core hyperv bus code, and the utility driver, the rest still have some review to get through by the various subsystem maintainers. Signed-off-by:
K. Y. Srinivasan <kys@microsoft.com>
-
K. Y. Srinivasan authored
net_dev is being de-referenced without proper checking; fix it. Signed-off-by:
Haiyang Zhang <haiyangz@microsoft.com> Reported-by:
Dan Carpenter <dan.carpenter@oracle.com> Signed-off-by:
-
Olaf Hering authored
Some commands sent by smartd will offline the device. With this change applied, smartd sill not monitor the device anymore. Signed-off-by:
Olaf Hering <olaf@aepfle.de> Acked-by:
-
K. Y. Srinivasan authored
Invoke cn_netlink_send() in a work context as opposed being called in the context of channel callback. On entry into the channel callback code the channel inbound spin lock is held and deferring to a work context avoids having to invoke cn_netlink_send() while holding the inbound lock. As part of this adjustment, also increase the timeout value for waiting for the user level component of KVP. Signed-off-by:
-
K. Y. Srinivasan authored
The host gurantees that there can be only one kvp transaction active against the guest. So, the transaction active state is needed only to protect against spurious user level calls. The current code had a race condition where the guest could prematurely return because the previous transaction state was not cleared - this state was being cleared after sending the response to the host and there was a window where the host could notify the guest of a new transaction before the transaction active state was properly set. Also deal with the case when the user mode component does not respond in a timely fashion correctly. I would like to thank Long Li <longli@microsoft.com> for identifying the problem. Signed-off-by:
Long Li <longli@microsoft.com> Signed-off-by:
-
- 05 Oct, 2011 31 commits
-
-
Jonathan Cameron authored
Basically make use of the gpio array functions. Technically the free doesn't need as much info as given here, but this keeps it clean and easy to follow. Signed-off-by:
Jonathan Cameron <jic23@cam.ac.uk> Acked-by:
Michael Hennerich <michael.hennerich@analog.com> Signed-off-by:
-
Jonathan Cameron authored
This should never have been exposed to userspace Signed-off-by:
-
Jonathan Cameron authored
Just convert the raw reads in this patch. Signed-off-by:
-
Jonathan Cameron authored
This is needed to ensure the required name attribute is created. Using an id table is the route most consistent with other drivers. Signed-off-by:
-
Jonathan Cameron authored
There are far too many possible part numbers that are not covered in here to have such a generic name. So move to naming after one of the supported parts. Signed-off-by:
-
Jonathan Cameron authored
Straight forward conversion. Signed-off-by:
-
Jonathan Cameron authored
Follows directly from change made in previous patch. Signed-off-by:
-
Jonathan Cameron authored
Ensure naming reflects what is measured, not how it is done. Resolvers can measure the same thing for starters. IIO_GYRO->IIO_ANGL_VEL to ensure consistent naming. Signed-off-by:
-
Jonathan Cameron authored
Trivial conversion. Signed-off-by:
-
Jonathan Cameron authored
Scraps the pointless name define and adds an id table. It's not technically required in drivers with only one supported part but it does make the probe code more consistent. Signed-off-by:
-
Jonathan Cameron authored
When the new allocation code was introduced a stray pointer to iio_dev structure was left in the chip state structure. This was never set but was then registered with the core. Signed-off-by:
-
Jonathan Cameron authored
No functional change, just a trivial tidy up so all drivers do the same thing. Signed-off-by:
-
Jonathan Cameron authored
Driver ported over to hwmon where it fits much better. Signed-off-by:
-
Franky Lin authored
Absorb related code into brcmf_add_if/brcmf_del_if. This is part of the net device interface clean up. Reviewed-by:
Roland Vossen <rvossen@broadcom.com> Reviewed-by:
Arend van Spriel <arend@broadcom.com> Signed-off-by:
-
Franky Lin authored
Some elements in structure brcmf_if are unused at all or redundant. This patch cleans it up. Reviewed-by:
-
Arend van Spriel authored
Throughout the data structures within the driver several references to the driver variables were stored. As the storage and access functions are now consolidated into srom.c those references are no longer needed and have been removed. Reviewed-by:
Alwin Beukers <alwin@broadcom.com> Signed-off-by:
-
Arend van Spriel authored
The function is called once with parameter 'off' fixed to zero. This parameter has been removed. Reviewed-by:
-
Arend van Spriel authored
The storage of variables obtained from srom are now stored in a linked list and lookup is done based on the enumerated identifier. Reported-by:
Johannes Berg <johannes@sipsolutions.net> Reviewed-by:
-
Arend van Spriel authored
In the srom variable tables fields were identified using string identifiers. This has been replaced by enumeration identifiers. Reported-by:
-
Arend van Spriel authored
The driver variables from srom are stored in memory with string identifiers and the caller needed to use this string identifier to retrieve a driver variable. The commit changes the calling code replacing strings with enumerated identifiers. Reported-by:
Pieter-Paul Giesberts <pieterpg@broadcom.com> Reviewed-by:
-
Arend van Spriel authored
In the driver several driver variables were looked up that are not supported by the srom code. These have been removed. Reviewed-by:
Brett Rudley <brudley@broadcom.com> Signed-off-by:
-
Arend van Spriel authored
The function brcmf_sdbrcm_bus_stop() terminates the watchdog and dpc thread, but this function can be called from the dpc thread itself. Stopping the dpc thread is only done when it is not the 'current' thread. Reviewed-by:
Franky (Zhenhui) Lin <frankyl@broadcom.com> Reviewed-by:
-
Arend van Spriel authored
The driver contained locking macros which map directly to the lock function provided by the kernel. It does not provide any additional value so these have been removed. Reported-by:
-
Arend van Spriel authored
The functions getvar() and getintvar() had to pass the buffer containing the driver variables. Now they pass the structure containing this buffer hiding what type of buffer/container is used for storing the driver variables. Reviewed-by:
-
Arend van Spriel authored
The phy code used its own driver variable lookup functions which were duplicates of those in the brcmsmac driver (in srom.c). The phy code now uses the functions in srom.c through the phy_shim interface. Reviewed-by:
-
Franky Lin authored
Remove some single line functions for bus register/unregister interface Reviewed-by:
-
Franky Lin authored
threads_only is always true as we never use the tasklet implementation. So related code is removed. Reviewed-by:
-
Arend van Spriel authored
The driver uses variables which are stored in string format. Using strings as variable identifiers is disliked by the community. The driver has been cleaned up and the only module providing these variables is srom.c. The variable retrieval functions have been moved to srom.c in preparation of a more likable way to store and lookup these driver variables. Reported-by:
-
Roland Vossen authored
A bug was introduced by the following commit (Sep 13): staging: brcm80211: use endian annotated structures in brcmsmac Result was that 64 bits systems will not be able to acquire an IP address. Also the rmmod crashed. This has been fixed and retested on a Sparc64. Reviewed-by: -
Roland Vossen authored
Dpc and timer events can now be traced. Combined with Mac80211 driver callback tracing, all entry points into the driver can now be traced. Reported-by:
-
Alwin Beukers authored
Removed the brcms_c_nmode_validate function as it only checks N-mode capability, which should always be true. Reviewed-by:
-
