Re: [PATCH] megaraid_sas: Fix the search of first memory bar

2016-08-30 Thread Martin K. Petersen
> "Christophe" == Christophe JAILLET writes: Christophe> The 2nd parameter of 'find_first_bit' is the number of bits Christophe> to search. In this case, we are passing 'sizeof(unsigned Christophe> long)' which is likely to be 4. Christophe> It is likely that the number of bits in a long wa

RE: [PATCH] megaraid_sas: Fix the search of first memory bar

2016-08-25 Thread Sumit Saxena
>Cc: megaraidlinux@avagotech.com; linux-s...@vger.kernel.org; linux- >ker...@vger.kernel.org; kernel-janit...@vger.kernel.org; Christophe JAILLET >Subject: [PATCH] megaraid_sas: Fix the search of first memory bar > >The 2nd parameter of 'find_first_bit' is the number of bi

Re: [PATCH] megaraid_sas: Fix the search of first memory bar

2016-08-25 Thread Martin K. Petersen
> "Christophe" == Christophe JAILLET writes: Christophe> The 2nd parameter of 'find_first_bit' is the number of bits Christophe> to search. In this case, we are passing 'sizeof(unsigned Christophe> long)' which is likely to be 4. Kashyap? Sumit? -- Martin K. Petersen Oracle Linux Eng

[PATCH] megaraid_sas: Fix the search of first memory bar

2016-08-21 Thread Christophe JAILLET
The 2nd parameter of 'find_first_bit' is the number of bits to search. In this case, we are passing 'sizeof(unsigned long)' which is likely to be 4. It is likely that the number of bits in a long was expected here, so use BITS_PER_LONG instead. Signed-off-by: Christophe JAILLET --- Other options