From: Sumit Saxena <sumit.saxena@avagotech.com>
To: Christoph Hellwig <hch@infradead.org>, Tomas Henzl <thenzl@redhat.com>
Cc: linux-scsi@vger.kernel.org, martin.petersen@oracle.com,
jbottomley@parallels.com,
Kashyap Desai <kashyap.desai@avagotech.com>
Subject: RE: [PATCH RESEND 18/18] megaraid_sas : swap whole register in megasas_register_aen
Date: Tue, 21 Apr 2015 18:12:01 +0530 [thread overview]
Message-ID: <17496cfabed5e1d59145d3f120fcff30@mail.gmail.com> (raw)
In-Reply-To: <20150421123719.GA7205@infradead.org>
>-----Original Message-----
>From: Christoph Hellwig [mailto:hch@infradead.org]
>Sent: Tuesday, April 21, 2015 6:07 PM
>To: Tomas Henzl
>Cc: Sumit.Saxena@avagotech.com; linux-scsi@vger.kernel.org;
>martin.petersen@oracle.com; hch@infradead.org;
>jbottomley@parallels.com; kashyap.desai@avagotech.com
>Subject: Re: [PATCH RESEND 18/18] megaraid_sas : swap whole register in
>megasas_register_aen
>
>On Tue, Apr 21, 2015 at 02:33:12PM +0200, Tomas Henzl wrote:
>> On 04/20/2015 02:35 PM, Sumit.Saxena@avagotech.com wrote:
>> > Swap the whole 32 bits we read from the hardware instead of swapping
>> > just the 16bits we care about in place later.
>> >
>> > Signed-off-by: Christoph Hellwig <hch@lst.de>
>> > ---
>> > drivers/scsi/megaraid/megaraid_sas_base.c | 5 +++--
>> > 1 files changed, 3 insertions(+), 2 deletions(-)
>> >
>> > diff --git a/drivers/scsi/megaraid/megaraid_sas_base.c
>> > b/drivers/scsi/megaraid/megaraid_sas_base.c
>> > index e863701..fa6c3c9 100644
>> > --- a/drivers/scsi/megaraid/megaraid_sas_base.c
>> > +++ b/drivers/scsi/megaraid/megaraid_sas_base.c
>> > @@ -4923,8 +4923,9 @@ megasas_register_aen(struct megasas_instance
>> > *instance, u32 seq_num,
>> >
>> > if (instance->aen_cmd) {
>> >
>> > - prev_aen.word = instance->aen_cmd->frame-
>>dcmd.mbox.w[1];
>> > - prev_aen.members.locale =
>le16_to_cpu(prev_aen.members.locale);
>> > + prev_aen.word =
>> > + le32_to_cpu(instance->aen_cmd->frame-
>>dcmd.mbox.w[1]);
>> > + prev_aen.members.locale = prev_aen.members.locale;
>>
>> This^ looks odd, do we need the last assignment?
>
>Obviously not, I was just in mechnical mode when doing this.
>
>It can be dropped for the repost.
Will drop it in resubmission of the patch.
prev parent reply other threads:[~2015-04-21 12:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-20 12:35 [PATCH RESEND 18/18] megaraid_sas : swap whole register in megasas_register_aen Sumit.Saxena
2015-04-21 10:33 ` Hannes Reinecke
2015-04-21 12:33 ` Tomas Henzl
2015-04-21 12:37 ` Christoph Hellwig
2015-04-21 12:42 ` Sumit Saxena [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=17496cfabed5e1d59145d3f120fcff30@mail.gmail.com \
--to=sumit.saxena@avagotech.com \
--cc=hch@infradead.org \
--cc=jbottomley@parallels.com \
--cc=kashyap.desai@avagotech.com \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=thenzl@redhat.com \
/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