- 16 Sep, 2011 29 commits
-
-
David Kilroy authored
For now just remove from hcfcfg.h, we will slowly remove the unused configurations as we go Signed-off-by:
David Kilroy <kilroyd@googlemail.com> Signed-off-by:
Greg Kroah-Hartman <gregkh@suse.de>
-
Jonathan Cameron authored
The recent reorganization of the sysfs attribute registration had the side effect of moving iio_device_register after registration of triggers etc. The side effect of this is that the id hadn't been allocated by the time of trigger registration. Thus all triggers based on device got the name <dev_name>-dev0 instead of <dev_name>-devN where N is the iio device id. This should also fix the lack of device name for some error messages that we have been seeing (and I'd been meaning to track down) as that has now moved earlier as well. Reported-by:
Manuel Stahl <manuel.stahl@iis.fraunhofer.de> Signed-off-by:
Jonathan Cameron <jic23@cam.ac.uk> Tested-by:
-
Jonathan Cameron authored
Cleaner and more consistent naming + makes one abi element we don't need go away. Signed-off-by:
-
Jonathan Cameron authored
This patch set should bring all the attributes created outside of chan_spec registration inline with the new abi. Signed-off-by:
Michael Hennerich <michael.hennerich@analog.com> Signed-off-by:
-
Aaro Koskinen authored
There are no build warnings at the moment. Signed-off-by:
Aaro Koskinen <aaro.koskinen@iki.fi> Signed-off-by:
-
Aaro Koskinen authored
Add a missing include to eliminate the following sparse warning: drivers/staging/xgifb/vb_table.h:2572:28: warning: symbol 'XGI21_LCDCapList' was not declared. Should it be static? Signed-off-by:
-
Aaro Koskinen authored
Use readl() and writel() in FB memory test instead of direct pointer access, and also add iomem annotations for the FB memory. The patch eliminates the following sparse warnings: drivers/staging/xgifb/XGI_main_26.c:2113:69: warning: incorrect type in assignment (different address spaces) drivers/staging/xgifb/XGI_main_26.c:2113:69: expected unsigned char *static [addressable] [toplevel] [assigned] pjVideoMemoryAddress drivers/staging/xgifb/XGI_main_26.c:2113:69: got void [noderef] <asn:2>* drivers/staging/xgifb/XGI_main_26.c:2399:30: warning: incorrect type in assignment (different address spaces) drivers/staging/xgifb/XGI_main_26.c:2399:30: expected char [noderef] <asn:2>*screen_base drivers/staging/xgifb/XGI_main_26.c:2399:30: got char *[addressable] [toplevel] [assigned] video_vbase drivers/staging/xgifb/XGI_main_26.c:2430:31: warning: incorrect type in argument 1 (different address spaces) drivers/staging/xgifb/XGI_main_26.c:2430:31: expected void volatile [noderef] <asn:2>*addr drivers/staging/xgifb/XGI_main_26.c:2430:31: got char *[addressable] [toplevel] [assigned] video_vbase drivers/staging/xgifb/XGI_main_26.c:2454:31: warning: incorrect type in argument 1 (different address spaces) drivers/staging/xgifb/XGI_main_26.c:2454:31: expected void volatile [noderef] <asn:2>*addr drivers/staging/xgifb/XGI_main_26.c:2454:31: got char *[addressable] [toplev Signed-off-by:
-
Aaro Koskinen authored
Include Linux headers before driver's own headers. Signed-off-by:
-
Aaro Koskinen authored
Use readb()/readw() instead of direct pointer access to read I/O mapped memory and also add __iomem annotation. The patch eliminates the following sparse warnings: drivers/staging/xgifb/XGI_main_26.c:2125:35: warning: incorrect type in assignment (different address spaces) drivers/staging/xgifb/XGI_main_26.c:2125:35: expected char *[addressable] [toplevel] [assigned] mmio_vbase drivers/staging/xgifb/XGI_main_26.c:2125:35: got void [noderef] <asn:2>* drivers/staging/xgifb/XGI_main_26.c:2439:31: warning: incorrect type in argument 1 (different address spaces) drivers/staging/xgifb/XGI_main_26.c:2439:31: expected void volatile [noderef] <asn:2>*addr drivers/staging/xgifb/XGI_main_26.c:2439:31: got char *[addressable] [toplevel] [assigned] mmio_vbase drivers/staging/xgifb/XGI_main_26.c:2463:31: warning: incorrect type in argument 1 (different address spaces) drivers/staging/xgifb/XGI_main_26.c:2463:31: expected void volatile [noderef] <asn:2>*addr drivers/staging/xgifb/XGI_main_26.c:2463:31: got char *[addressable] [toplevel] [assigned] mmio_vbase Signed-off-by:
-
Arvydas Sidorenko authored
Not much left out of this header file. All these typedefs can be found in stdint.h Signed-off-by:
Arvydas Sidorenko <asido4@gmail.com> Signed-off-by:
-
Yong Zhang authored
This flag is a NOOP and can be removed now. Signed-off-by:
Yong Zhang <yong.zhang0@gmail.com> Signed-off-by:
-
K. Y. Srinivasan authored
Consistently name the variable tracking the link status. Use a consistent type for this variable and get rid of some unnecessary parentheses as well. I would like to thank Joe Perches <joe@perches.com> for suggesting these changes and patiently helping me get here! Signed-off-by:
K. Y. Srinivasan <kys@microsoft.com> Signed-off-by:
Haiyang Zhang <haiyangz@microsoft.com> Signed-off-by:
-
K. Y. Srinivasan authored
Rename deviceInfo as device_info. Signed-off-by:
-
K. Y. Srinivasan authored
Rename rndisDevice to rndis_device. Signed-off-by:
-
K. Y. Srinivasan authored
Rename netDevice as net_device. Signed-off-by:
-
K. Y. Srinivasan authored
Hyper-V modules can be built as part of the kernel (not just as modules). Get rid of the module dependency in Kconfig. Signed-off-by:
-
K. Y. Srinivasan authored
struct hv_device_info is about 101 bytes in size. Do not allocate this structure on the stack. Signed-off-by:
-
K. Y. Srinivasan authored
Now that we have eliminated all uses of the ext field in struct hv_device, get rid of the ext field. Signed-off-by:
-
K. Y. Srinivasan authored
Get rid of the usage of the ext field in struct hv_device for the mouse driver. We do this by using the newly introduced functions to set and and get driver specific data. Signed-off-by:
-
K. Y. Srinivasan authored
Now, eliminate the usage of ext field in struct hv_device for netvsc driver. We do this by registering pointer to struct netvsc_device as the driver specific data and eliminating the current usage of driver specific data to save and retrieve the pointer to struct net_device. Additionally, all access to the driver specific data is through the vmbus wrapper functions. As part of this cleanup, we also get rid of some unnecessary debug print statements. Signed-off-by:
-
K. Y. Srinivasan authored
Now, eliminate the usage of ext field in struct hv_device for storvsc driver. We do this by registering pointer to struct storvsc_device as the driver specific data and eliminating the current usage of driver specific data to save and retrieve the pointer to struct Scsi_Host. Additionally, all access to the driver specific data is through the vmbus wrapper functions. Note that function to allocate the host gives us a reference on the host object. Signed-off-by:
-
K. Y. Srinivasan authored
Now, get rid of some unnecessary state and definitions. Signed-off-by:
-
K. Y. Srinivasan authored
Get rid of alloc_stor_device() by inlining the code. Signed-off-by:
-
K. Y. Srinivasan authored
Get rid of storvsc_dev_add() by inlining the code. Signed-off-by:
-
K. Y. Srinivasan authored
vmbus_remove() cannot fail; clean it up accordingly. Signed-off-by:
-
K. Y. Srinivasan authored
Introduce vmbus specific wrapper functions to set/get driver specific data. Signed-off-by:
-
K. Y. Srinivasan authored
Use the driver_data to identify ide devices in storvsc_probe(). Signed-off-by:
-
K. Y. Srinivasan authored
In preparation to leveraging the driver_data field in struct hv_vmbus_device_id, change the signature of struct hv_driver probe function. Signed-off-by:
-
K. Y. Srinivasan authored
Introduce a utility function to match hv_vmbus_device_id. Signed-off-by:
-
- 12 Sep, 2011 11 commits
-
-
Mark Brown authored
Signed-off-by:
Lu Guanqun <guanqun.lu@intel.com> Cc: Vinod Koul <vinod.koul@intel.com> Acked-by:
Vinod Koul <vinod.koul@intel.com> Acked-by:
Liam Girdwood <lrg@ti.com> Acked-by:
Mark Brown <broonie@opensource.wolfsonmicro.com> Signed-off-by:
-
Franky Lin authored
Reshuffle function order in wl_cfg80211 of fullmac to get rid of static function declaration Reported-by:
Johannes Berg <johannes@sipsolutions.net> Reviewed-by:
Arend van Spriel <arend@broadcom.com> Reviewed-by:
Roland Vossen <rvossen@broadcom.com> Signed-off-by:
-
Roland Vossen authored
Alloc.c does not contain enough functionality anymore to warrant its own file. Moved functionality into main.c Reported-by:
-
Roland Vossen authored
Members were always set to zero, or set but never read. Reviewed-by:
-
Roland Vossen authored
Struct member variables were only set to '0'. As a result, function brcms_c_local_constraint_qdbm() always returned BRCMS_TXPWR_MAX and thus could be removed. Reviewed-by:
-
Roland Vossen authored
Members were always set to zero, or set but never read. Signed-off-by:
-
Roland Vossen authored
Nothing useful was done with this struct. Signed-off-by:
-
Roland Vossen authored
Since the macro's IS_MCS(0), RSPEC_STF(0) and PHY_TXC1_MODE_SISO all expand to 0, inactive code could be removed. Signed-off-by:
-
Roland Vossen authored
This was unused. Signed-off-by:
-
Roland Vossen authored
Struct members were unused or only written but never read. Signed-off-by:
-
Roland Vossen authored
Removed unused mechanism as part of code cleanup. Signed-off-by:
-
