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: Tue, 10 Jan 2012 11:33:18 -0800 [thread overview]
Message-ID: <1326223998.14089.26.camel@haakon2.linux-iscsi.org> (raw)
In-Reply-To: <CAO+b5-qs3fE8yZaKQ+kzpsSsX1PyXE09wBzxnUi55GZ5j4TJKg@mail.gmail.com>
On Tue, 2012-01-10 at 19:19 +0000, Bart Van Assche wrote:
> 2012/1/10 Nicholas A. Bellinger <nab@linux-iscsi.org>
> > *) Initial merge for the SRP target (ib_srpt) fabric module (bart)
>
> As far as I know the last time that patch was posted for review is
> November 4 (http://permalink.gmane.org/gmane.linux.scsi.target.devel/420).
> The date of the ib_srpt commit is December 16
> (http://git.kernel.org/?p=linux/kernel/git/nab/target-pending.git;a=commitdiff;h=a42d985bd5b234da8b61347a78dc3057bf7bb94d).
> The two patches aren't identical. That makes me wonder whether that
> patch should have been reposted for review ?
>
Hi Bart,
The changes since the Nov 4 RFC are listed in the patch commit log:
ib_srpt: Make compilation with BUG=n proceed`
ib_srpt: Use new target_core_fabric.h include
ib_srpt: Check hex2bin() return code to silence build warning
These are all very minor and did not warrant another full RFC posting.
--nab
next prev parent reply other threads:[~2012-01-10 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 [this message]
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
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=1326223998.14089.26.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
all inboxes | Powered by JetHome®