mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Nicholas A. Bellinger" <nab@linux-iscsi.org>
To: Bart Van Assche <bvanassche@acm.org>
Cc: "Linus Torvalds" <torvalds@linux-foundation.org>,
	target-devel <target-devel@vger.kernel.org>,
	linux-scsi <linux-scsi@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	"Christoph Hellwig" <hch@lst.de>,
	"Roland Dreier" <roland@kernel.org>,
	"Jörn Engel" <joern@purestorage.com>,
	"Sebastian Andrzej Siewior" <bigeasy@linutronix.de>
Subject: Re: [GIT PULL] target: Updates for v3.3-rc1 (round 1)
Date: Wed, 11 Jan 2012 11:32:57 -0800	[thread overview]
Message-ID: <1326310377.20199.16.camel@haakon2.linux-iscsi.org> (raw)
In-Reply-To: <CAO+b5-oqsimTj6fRa=euEegH8Sqg=N_j4vXs6u=j31Za+WBKOw@mail.gmail.com>

On Wed, 2012-01-11 at 07:57 +0100, Bart Van Assche wrote:
> 2012/1/10 Nicholas A. Bellinger <nab@linux-iscsi.org>:
> > These are all very minor and did not warrant another full RFC posting.
> 
> There is a reason why the ib_srpt patch should have been reposted:
> Last WQE handling is still wrong, despite a patch being available
> (http://www.spinics.net/lists/linux-rdma/msg09982.html).
> 

This patch was applied to lio-core.git, but considering that I've
received zero testing feedback on this I elected not to include it in
target-pending for the initial merge.

Once it can get some real testing it will be included into rc-fixes
along with the rest of the post merge-window updates.  So please, lets
not try to delay the merging of this driver (again) over bits that will
be addressed post -rc1.

Thanks,

--nab





  reply	other threads:[~2012-01-11 19:33 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-10 18:56 Nicholas A. Bellinger
2012-01-10 19:19 ` Bart Van Assche
2012-01-10 19:33   ` Nicholas A. Bellinger
2012-01-10 19:51     ` James Bottomley
2012-01-10 21:04       ` Nicholas A. Bellinger
2012-01-11 10:49       ` Christoph Hellwig
2012-01-14 15:19         ` James Bottomley
2012-01-11  6:57     ` Bart Van Assche
2012-01-11 19:32       ` Nicholas A. Bellinger [this message]
2012-01-13 23:02 ` Nicholas A. Bellinger

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=1326310377.20199.16.camel@haakon2.linux-iscsi.org \
    --to=nab@linux-iscsi.org \
    --cc=bigeasy@linutronix.de \
    --cc=bvanassche@acm.org \
    --cc=hch@lst.de \
    --cc=joern@purestorage.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=roland@kernel.org \
    --cc=target-devel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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
Powered by JetHome