Re: [PATCH] staging: lustre: Fix sparse warning on address-space

2015-01-17 Thread Greg Kroah-Hartman
On Mon, Dec 29, 2014 at 08:49:40PM +0800, Jia He wrote: > This patch is to fix the below warnings generated by sparse: > warning: incorrect type in argument 1 (different address spaces) > expected void const volatile [noderef] * > got int * > Adding the macro "__user" can suppress the warnings,

Re: [PATCH] staging: lustre: Fix sparse warning on address-space

2015-01-17 Thread Greg Kroah-Hartman
On Mon, Dec 29, 2014 at 08:49:40PM +0800, Jia He wrote: This patch is to fix the below warnings generated by sparse: warning: incorrect type in argument 1 (different address spaces) expected void const volatile [noderef] asn:1*noident got int *noident Adding the macro __user can suppress

Re: [PATCH] staging: lustre: Fix sparse warning on address-space

2015-01-13 Thread hejianet
Hi all Ping again, any comments are welcome Justin On Mon, 29 Dec 2014 20:49:40 +0800 from hejia...@gmail.com wrote: > This patch is to fix the below warnings generated by sparse: > warning: incorrect type in argument 1 (different address spaces) > expected void const volatile [noderef] * >

Re: [PATCH] staging: lustre: Fix sparse warning on address-space

2015-01-13 Thread hejianet
Hi all Ping again, any comments are welcome Justin On Mon, 29 Dec 2014 20:49:40 +0800 from hejia...@gmail.com wrote: This patch is to fix the below warnings generated by sparse: warning: incorrect type in argument 1 (different address spaces) expected void const volatile [noderef]

[PATCH] staging: lustre: Fix sparse warning on address-space

2014-12-29 Thread Jia He
This patch is to fix the below warnings generated by sparse: warning: incorrect type in argument 1 (different address spaces) expected void const volatile [noderef] * got int * Adding the macro "__user" can suppress the warnings, and aslo some lines are adjusted for 80 chars line limitation.

[PATCH] staging: lustre: Fix sparse warning on address-space

2014-12-29 Thread Jia He
This patch is to fix the below warnings generated by sparse: warning: incorrect type in argument 1 (different address spaces) expected void const volatile [noderef] asn:1*noident got int *noident Adding the macro __user can suppress the warnings, and aslo some lines are adjusted for 80 chars