From: Christoph Hellwig <hch@infradead.org>
To: Ben Hutchings <ben@decadent.org.uk>
Cc: "James E.J. Bottomley" <JBottomley@parallels.com>,
Anil Gurumurthy <agurumur@brocade.com>,
Vijaya Mohan Guvva <vmohan@brocade.com>,
linux-scsi <linux-scsi@vger.kernel.org>,
stable <stable@vger.kernel.org>
Subject: Re: [PATCH RESEND] [SCSI] bfa: Fix undefined bit shift on big-endian architectures with 32-bit DMA address
Date: Wed, 25 Jun 2014 13:12:24 +0200 [thread overview]
Message-ID: <20140625111224.GA19415@infradead.org> (raw)
In-Reply-To: <1402266805.23860.40.camel@deadeye.wl.decadent.org.uk>
Looks good,
Reviewed-by: Christoph Hellwig <hch@lst.de>
Can I get another review, too please?
next prev parent reply other threads:[~2014-06-25 11:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-08 22:33 [PATCH RESEND] [SCSI] bfa: Fix undefined bit shift on big-endian architectures with 32-bit DMA address Ben Hutchings
2014-06-25 11:12 ` Christoph Hellwig [this message]
2014-06-26 2:21 ` Martin K. Petersen
2014-06-26 5:23 ` Anil Gurumurthy
-- strict thread matches above, loose matches on Subject: below --
2014-06-08 23:48 Ben Hutchings
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=20140625111224.GA19415@infradead.org \
--to=hch@infradead.org \
--cc=JBottomley@parallels.com \
--cc=agurumur@brocade.com \
--cc=ben@decadent.org.uk \
--cc=linux-scsi@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=vmohan@brocade.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