RE: [PATCH 1/1] aacraid: don't assign cpu_to_le32(int) to u8

2007-11-08 Thread Salyzyn, Mark
Andreas Schwab; Stephen Rothwell; > linux-scsi@vger.kernel.org; LKML > Subject: Re: [PATCH 1/1] aacraid: don't assign cpu_to_le32(int) to u8 > > On Wed, Nov 07, 2007 at 01:51:44PM -0500, Salyzyn, Mark wrote: > > Christoph Hellwig [mailto:[EMAIL PROTECTED] sez: > > &

Re: [PATCH 1/1] aacraid: don't assign cpu_to_le32(int) to u8

2007-11-08 Thread Christoph Hellwig
On Wed, Nov 07, 2007 at 01:51:44PM -0500, Salyzyn, Mark wrote: > Christoph Hellwig [mailto:[EMAIL PROTECTED] sez: > > Did anyone run the driver through sparse to see if we have > > more issues like this? > > There are some warnings from sparse, none like this one. I will deal > with the warnings

RE: [PATCH 1/1] aacraid: don't assign cpu_to_le32(int) to u8

2007-11-07 Thread Salyzyn, Mark
Christoph Hellwig [mailto:[EMAIL PROTECTED] sez: > Did anyone run the driver through sparse to see if we have > more issues like this? There are some warnings from sparse, none like this one. I will deal with the warnings ... Sincerely -- Mark Salyzyn - To unsubscribe from this list: send the l

Re: [PATCH 1/1] aacraid: don't assign cpu_to_le32(int) to u8

2007-11-07 Thread Christoph Hellwig
On Wed, Nov 07, 2007 at 10:58:12AM -0500, Salyzyn, Mark wrote: > Good point, thanks. The intent of the management applications > utilization of this AIF report is to observe the LSB of the value of > integer value in BlinkLED. The actions of the cpu_to_le32 actually > breaks this and reports the wr