From: Mike Christie <michaelc@cs.wisc.edu>
To: Christoph Hellwig <hch@infradead.org>
Cc: James Bottomley <James.Bottomley@HansenPartnership.com>,
Hannes Reinecke <hare@suse.de>,
linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
Vikas Chaudhary <vikas.chaudhary@qlogic.com>
Subject: Re: [ANNOUNCE] scsi patch queue tree
Date: Wed, 28 May 2014 11:04:31 -0500 [thread overview]
Message-ID: <5386090F.9060004@cs.wisc.edu> (raw)
In-Reply-To: <20140528155008.GA6913@infradead.org>
On 05/28/2014 10:50 AM, Christoph Hellwig wrote:
> On Wed, May 28, 2014 at 10:37:31AM -0500, Mike Christie wrote:
>> On 05/28/2014 05:54 AM, Christoph Hellwig wrote:
>>> be2iscsi: Fix processing cqe for cxn whose endpoint is freed
>>
>> I didn't look at your tree, but when this patch was posted on the list I
>> think it had a bug.
>>
>> http://www.spinics.net/lists/linux-scsi/msg74191.html
>
> I read through it and saw your comment, but so far it seems the patch
> and especially the series does more good than harm.
Did you see these patchsets:
[PATCH 00/10] qla4xxx: 5.04.00-k5: Updates for scsi "misc" branch
and
[PATCH 0/6] qla4xxx: 5.04.00-k6: Updates for scsi "misc" branch
? I think they should be ok for your tree if you did not see any issues
with them.
next prev parent reply other threads:[~2014-05-28 16:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-19 14:06 Christoph Hellwig
2014-05-20 0:03 ` Stephen Rothwell
2014-05-20 5:39 ` Christoph Hellwig
2014-05-20 23:46 ` Stephen Rothwell
2014-05-21 2:25 ` James Bottomley
2014-05-28 10:54 ` Christoph Hellwig
2014-05-28 15:37 ` Mike Christie
2014-05-28 15:50 ` Christoph Hellwig
2014-05-28 16:04 ` Mike Christie [this message]
2014-05-28 16:05 ` Christoph Hellwig
2014-05-28 16:01 ` Sujit Reddy Thumma
2014-05-28 16:03 ` Christoph Hellwig
2014-06-11 12:01 ` Christoph Hellwig
2014-06-11 14:17 ` James Bottomley
2014-06-11 14:31 ` Christoph Hellwig
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=5386090F.9060004@cs.wisc.edu \
--to=michaelc@cs.wisc.edu \
--cc=James.Bottomley@HansenPartnership.com \
--cc=hare@suse.de \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=vikas.chaudhary@qlogic.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
Powered by JetHome