- 19 Jun, 2016 27 commits
-
-
Oleg Drokin authored
When OpenSFS took over lustre.org, there was some reshuffling. FIDs on ZFS document is now at http://wiki.old.lustre.org/index.php/Architecture_-_Interoperability_fids_zfs instead of the old location, so update comments accordingly. Signed-off-by:
Oleg Drokin <green@linuxhacker.ru> Reported-by:
Xose Vazquez Perez <xose.vazquez@gmail.com> Signed-off-by:
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
-
Oleg Drokin authored
This patch fixes all checkpatch occurences of "CHECK: No space is necessary after a cast" in Lustre code. Signed-off-by:
Emoly Liu <emoly.liu@intel.com> Signed-off-by:
-
Emoly Liu authored
This patch fixes all checkpatch occurences of "CHECK: Logical continuations should be on the previous line" in Lustre code. Signed-off-by:
-
Emoly Liu authored
This patch fixes one checkpatch warning in lustre: WARNING: EXPORT_SYMBOL(foo); should immediately follow its function/variable Signed-off-by:
-
Binoy Jayan authored
The semaphore 'rf_sem' in rtl8192u has no users, hence removing it. Signed-off-by:
Binoy Jayan <binoy.jayan@linaro.org> Signed-off-by:
-
Binoy Jayan authored
The semaphore 'scan_sem' in rtl8192u is a simple mutex, so it should be written as one. Semaphores are going away in the future. Signed-off-by:
-
Binoy Jayan authored
The semaphore 'wx_sem' in ieee80211_device is a simple mutex, so it should be written as one. Semaphores are going away in the future. Signed-off-by:
-
Binoy Jayan authored
The semaphore 'wx_sem' in r8192_priv is a simple mutex, so it should be written as one. Semaphores are going away in the future. Signed-off-by:
-
Salah Triki authored
Propagate errors from kzalloc and usb_control_msg and change the return type of write_nic_dword from void to int. Signed-off-by:
Salah Triki <salah.triki@acm.org> Signed-off-by:
-
Salah Triki authored
Propagate errors from kzalloc and usb_control_msg and change the return type of write_nic_word from void to int. Signed-off-by:
-
Salah Triki authored
Propagate errors from kzalloc and usb_control_msg and change the return type of write_nic_byte_E from void to int. Signed-off-by:
-
Salah Triki authored
Propagate errors from kzalloc and usb_control_msg and change the return type of write_nic_byte from void to int. Signed-off-by:
-
Salah Triki authored
The call of rtl8192_read_eeprom_info may fail, therefore its return value must be checked and propagated in the case of error Signed-off-by:
-
Salah Triki authored
Propagate error from eprom_read and change the return type of rtl8192_read_eeprom_info from void to int. Signed-off-by:
-
Salah Triki authored
The call of eprom_read may fail, therefore its return value must be checked Signed-off-by:
-
Salah Triki authored
Propagate error from eprom_r and change the return type of eprom_read from u32 to int. Signed-off-by:
-
Salah Triki authored
The call of read_nic_word_E may fail, therefore its return value must be checked and propagated in the case of error. Signed-off-by:
-
Dan Carpenter authored
enc->rx_seq[] and enc->key[] are arrays, not pointers and they can't be NULL. Let's remove these NULL checks. Signed-off-by:
Dan Carpenter <dan.carpenter@oracle.com> Signed-off-by:
-
Wolfram Sang authored
We are upstream now, we don't need seperate driver versioning. Signed-off-by:
Wolfram Sang <wsa@the-dreams.de> Signed-off-by:
-
Wolfram Sang authored
Until we switch to cfg80211 (if ever), we must do this manually. Signed-off-by:
-
Wolfram Sang authored
There is no need to continue then. Also, this enables us to remove an ugly static variable. Signed-off-by:
-
Wolfram Sang authored
Move read/write functions to the top and driver struct to the end, so we can remove all forward declarations. Signed-off-by:
-
Wolfram Sang authored
No 79xx anymore, this is confusing. Add a comment saying that old versions were probably named 7910/79xx. Signed-off-by:
-
Wolfram Sang authored
So the module will be loaded automatically on card insertion. Rename the array while here. Signed-off-by:
-
Wolfram Sang authored
Includes probably need a driver-wide clean up, but for now let's at least group all includes from the sdio file together. Signed-off-by:
-
Wolfram Sang authored
Signed-off-by:
-
Wolfram Sang authored
I verified that all but two settings from the config file can be set up also via 'iwconfig' or 'iwpriv'. The two missing are ROM_FILE and PhyInformationTimer. ROM_FILE can be easily dropped. There is only one known firmware floating on the net, so, the name is fix and we can make this constant. Frankly, I don't know when PhyInformationTimer needs to be set to non-zero. But if we need it somewhen, there is already (currently commented out) code to add this as another private method, so we could use that. Summa summarum: We can remove the config file handling and the example config file. The only useful action, initialization of the configuration struct, is now moved to the sdio main file. Signed-off-by:
-
- 18 Jun, 2016 13 commits
-
-
Nicolai Stange authored
Since commit 49d200de ("debugfs: prevent access to removed files' private data"), a debugfs file's file_operations methods get proxied through lifetime aware wrappers. However, only a certain subset of the file_operations members is supported by debugfs and ->compat_ioctl isn't among them -- it appears to be NULL from the VFS layer's perspective. This behaviour breaks the /sys/kernel/debug/sync/sw_sync file introduced concurrently with commit a44eb74c ("staging/android: move SW_SYNC_USER to a debugfs file"). Since that file never gets removed, there is no file removal race and thus, a lifetime checking proxy isn't needed. Avoid the proxying for /sys/kernel/debug/sync/sw_sync by creating it via debugfs_create_file_unsafe() rather than debugfs_create_file(). For consistency, do the same for /sys/kernel/debug/sync/info. Fixes: 49d200de ("debugfs: prevent access to removed files' private data") Fixes: a44eb74c ("staging/android: move SW_SYNC_USER to a debugfs file") Signed-off-by:
Nicolai Stange <nicstange@gmail.com> Signed-off-by:
-
Gustavo Padovan authored
SW_SYNC only works with DEBUG_FS so state it in the Kconfig file. Signed-off-by:
Gustavo Padovan <gustavo.padovan@collabora.co.uk> Reviewed-by:
Daniel Vetter <daniel.vetter@ffwll.ch> Reviewed-by:
Sumit Semwal <sumit.semwal@linaro.org> Signed-off-by:
-
Gustavo Padovan authored
This header file only contains information for debugging and SW_SYNC, so rename it to sync_debug.h instead of having a more generic name. Signed-off-by:
-
Gustavo Padovan authored
As it is internal to sw_sync now this value will always be "sw_sync". Signed-off-by:
-
Gustavo Padovan authored
This function was just used by the file release function, so we just fold its content there and remove sync_timeline_destroy(). Signed-off-by:
-
Gustavo Padovan authored
'destroyed' was set but not used ny anyone. Signed-off-by:
-
Gustavo Padovan authored
We don't want to export this from the kernel. This is interface is only for testing and debug. So testers shall copy the ioctl info in their own projects. Signed-off-by:
-
Gustavo Padovan authored
The only use sync_timeline will have in upstream kernel is for debugging through the SW_SYNC interface. So make it internal to SW_SYNC to avoid people use it in the future. Signed-off-by:
-
Gustavo Padovan authored
Most of the includes there are not necessary anymore. Signed-off-by:
-
Gustavo Padovan authored
Split sync_debug and sw_sync in two different files. Signed-off-by:
-
Gustavo Padovan authored
Move the list_head members from sync_pt to struct fence was a mistake, they will not be used by struct fence as planned before, so here we create sync_pt again to bring the list heads back. Signed-off-by:
-
Gustavo Padovan authored
After we removed sw_sync_timeline this arg has not been really used by anyone, all its users pass the size of struct sync_timeline there. So simplify this function but not requiring the size anymore. Signed-off-by:
-
Gustavo Padovan authored
When we call sync_print_fence() fence is always valid. Signed-off-by:
-
