public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@SteelEye.com>
To: "Moore, Eric" <Eric.Moore@lsi.com>
Cc: akpm@linux-foundation.org, linux-scsi@vger.kernel.org, dmueller@osuse.de
Subject: RE: [patch 18/30] Fix |/|| confusion in fusion driver
Date: Tue, 08 May 2007 12:09:57 -0500	[thread overview]
Message-ID: <1178644197.3737.51.camel@mulgrave.il.steeleye.com> (raw)
In-Reply-To: <664A4EBB07F29743873A87CF62C26D7070C8E5@NAMAIL4.ad.lsil.com>

On Tue, 2007-05-08 at 11:06 -0600, Moore, Eric wrote:
> On Thursday, April 26, 2007 1:35 AM, Dirk Mueller wrote:
> 
> > 
> > This patch corrects a |/|| confusion in 
> > mptscsih_copy_sense_data.  Using ||
> > means that the data that ends up being written is (almost always) 1,
> > instead of being bit-wise or'ed.
> > 
> > Cc: Eric Moore <eric.moore@lsi.com>
> > Cc: James Bottomley <James.Bottomley@SteelEye.com>
> > Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
> > ---
> > 
> >  drivers/message/fusion/mptscsih.c |    6 +++---
> >  1 file changed, 3 insertions(+), 3 deletions(-)
> > 
> > diff -puN 
> > drivers/message/fusion/mptscsih.c~fix--confusion-in-fusion-dri
> > ver drivers/message/fusion/mptscsih.c
> > --- 
> > a/drivers/message/fusion/mptscsih.c~fix--confusion-in-fusion-driver
> > +++ a/drivers/message/fusion/mptscsih.c
> > @@ -2463,9 +2463,9 @@ mptscsih_copy_sense_data(struct scsi_cmn
> >  				ioc->events[idx].event = 
> > MPI_EVENT_SCSI_DEVICE_STATUS_CHANGE;
> >  				ioc->events[idx].eventContext = 
> > ioc->eventContext;
> >  
> > -				ioc->events[idx].data[0] = 
> > (pReq->LUN[1] << 24) ||
> > -					
> > (MPI_EVENT_SCSI_DEV_STAT_RC_SMART_DATA << 16) ||
> > -					(sc->device->channel << 
> > 8) || sc->device->id;
> > +				ioc->events[idx].data[0] = 
> > (pReq->LUN[1] << 24) |
> > +					
> > (MPI_EVENT_SCSI_DEV_STAT_RC_SMART_DATA << 16) |
> > +					(sc->device->channel << 
> > 8) | sc->device->id;
> >  
> >  				ioc->events[idx].data[1] = 
> > (sense_data[13] << 8) || sense_data[12];
> >  
> 
> 
> Thanks, I agree with the change, however shouldn't we be changing:
> 
> >  ioc->events[idx].data[1] = > (sense_data[13] << 8) || sense_data[12];
> >  
> 
> to
> 
> >  ioc->events[idx].data[1] = > (sense_data[13] << 8) | sense_data[12];
> >  
> 
> 
> And in the  mptbase.h, the definition of the struct should be changed
> from 
> 
> > typedef struct _mpt_ioctl_events {
> >	u32	event;		/* Specified by define above */
> >	u32	eventContext;	/* Index or counter */
> >	int	data[2];		/* First 8 bytes of Event Data
> */
> > } MPT_IOCTL_EVENTS;
> 
> to
> 
> > typedef struct _mpt_ioctl_events {
> >	u32	event;		/* Specified by define above */
> >	u32	eventContext;	/* Index or counter */
> >	u32	data[2];		/* First 8 bytes of Event Data
> */
> > } MPT_IOCTL_EVENTS;


Probably ... could you update the patch accordingly and send it in?

James



      reply	other threads:[~2007-05-08 17:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-26  7:35 [patch 18/30] Fix |/|| confusion in fusion driver akpm
2007-05-07 19:55 ` James Bottomley
2007-05-08 17:06 ` Moore, Eric
2007-05-08 17:09   ` James Bottomley [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1178644197.3737.51.camel@mulgrave.il.steeleye.com \
    --to=james.bottomley@steeleye.com \
    --cc=Eric.Moore@lsi.com \
    --cc=akpm@linux-foundation.org \
    --cc=dmueller@osuse.de \
    --cc=linux-scsi@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox