From: Christoph Hellwig <hch@infradead.org>
To: Mike Christie <michaelc@cs.wisc.edu>
Cc: Christoph Hellwig <hch@infradead.org>,
James Bottomley <James.Bottomley@HansenPartnership.com>,
Hannes Reinecke <hare@suse.de>,
linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [ANNOUNCE] scsi patch queue tree
Date: Wed, 28 May 2014 08:50:08 -0700 [thread overview]
Message-ID: <20140528155008.GA6913@infradead.org> (raw)
In-Reply-To: <538602BB.2080609@cs.wisc.edu>
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. I'll ping the
author again to get a fix for the issue you pointed out - I was planning
to do that anwyay.
next prev parent reply other threads:[~2014-05-28 15:50 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-19 14:06 [ANNOUNCE] scsi patch queue tree 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 [this message]
2014-05-28 16:04 ` Mike Christie
2014-05-28 16:05 ` Christoph Hellwig
2014-05-28 16:01 ` Sujit Reddy Thumma
2014-05-28 16:03 ` Christoph Hellwig
2014-06-02 7:58 ` Christoph Hellwig
2014-06-02 8:25 ` Boaz Harrosh
2014-06-02 8:26 ` Christoph Hellwig
2014-06-02 8:32 ` Boaz Harrosh
2014-06-11 12:01 ` Christoph Hellwig
2014-06-11 14:17 ` James Bottomley
2014-06-11 14:31 ` Christoph Hellwig
2014-06-24 15:52 ` Christoph Hellwig
2014-06-24 15:53 ` Christoph Hellwig
2014-06-25 12:41 ` 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=20140528155008.GA6913@infradead.org \
--to=hch@infradead.org \
--cc=James.Bottomley@HansenPartnership.com \
--cc=hare@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=michaelc@cs.wisc.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.