Re: [PATCH 01/16] ARM: warnings in arch/arm/include/asm/uaccess.h

2012-10-09 Thread Arnd Bergmann
On Monday 08 October 2012, Greg Ungerer wrote: > On 06/10/12 00:55, Arnd Bergmann wrote: > > On NOMMU ARM, the __addr_ok() and __range_ok() macros do not evaluate > > their arguments, which may lead to harmless build warnings in some > > code where the variables are not used otherwise. Adding a

Re: [PATCH 01/16] ARM: warnings in arch/arm/include/asm/uaccess.h

2012-10-09 Thread Arnd Bergmann
On Monday 08 October 2012, Greg Ungerer wrote: On 06/10/12 00:55, Arnd Bergmann wrote: On NOMMU ARM, the __addr_ok() and __range_ok() macros do not evaluate their arguments, which may lead to harmless build warnings in some code where the variables are not used otherwise. Adding a cast to

Re: [PATCH 01/16] ARM: warnings in arch/arm/include/asm/uaccess.h

2012-10-07 Thread Greg Ungerer
On 06/10/12 00:55, Arnd Bergmann wrote: On NOMMU ARM, the __addr_ok() and __range_ok() macros do not evaluate their arguments, which may lead to harmless build warnings in some code where the variables are not used otherwise. Adding a cast to void gets rid of the warning and does not make any

Re: [PATCH 01/16] ARM: warnings in arch/arm/include/asm/uaccess.h

2012-10-07 Thread Greg Ungerer
On 06/10/12 00:55, Arnd Bergmann wrote: On NOMMU ARM, the __addr_ok() and __range_ok() macros do not evaluate their arguments, which may lead to harmless build warnings in some code where the variables are not used otherwise. Adding a cast to void gets rid of the warning and does not make any

[PATCH 01/16] ARM: warnings in arch/arm/include/asm/uaccess.h

2012-10-05 Thread Arnd Bergmann
On NOMMU ARM, the __addr_ok() and __range_ok() macros do not evaluate their arguments, which may lead to harmless build warnings in some code where the variables are not used otherwise. Adding a cast to void gets rid of the warning and does not make any semantic changes. Without this patch,

[PATCH 01/16] ARM: warnings in arch/arm/include/asm/uaccess.h

2012-10-05 Thread Arnd Bergmann
On NOMMU ARM, the __addr_ok() and __range_ok() macros do not evaluate their arguments, which may lead to harmless build warnings in some code where the variables are not used otherwise. Adding a cast to void gets rid of the warning and does not make any semantic changes. Without this patch,