From: Roland Dreier <roland@kernel.org>
To: "Nicholas A. Bellinger" <nab@linux-iscsi.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>,
linux-rdma <linux-rdma@vger.kernel.org>,
Christoph Hellwig <hch@lst.de>,
Bart Van Assche <bvanassche@acm.org>
Subject: Re: [GIT PULL]: ib_srpt: Initial SRP target merge for v3.3-rc1
Date: Wed, 18 Jan 2012 10:06:57 -0800 [thread overview]
Message-ID: <CAL1RGDUifg_dD4JVO8O=z=JRrMcAdX1SM3iHwbeA4kBau0Ag5A@mail.gmail.com> (raw)
In-Reply-To: <1326836021.16983.38.camel@haakon2.linux-iscsi.org>
I think this is definitely OK to go upstream at this point ... we can do further
cleanups once upstream but there isn't anything close to a merge blocker
at this point.
Linus, this has been essentially unchanged since the 3.2 merge window.
Any way we can get this in the 3.3 cycle?
- R.
prev parent reply other threads:[~2012-01-18 18:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-17 21:33 [GIT PULL]: ib_srpt: Initial SRP target merge for v3.3-rc1 Nicholas A. Bellinger
2012-01-18 18:06 ` Roland Dreier [this message]
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='CAL1RGDUifg_dD4JVO8O=z=JRrMcAdX1SM3iHwbeA4kBau0Ag5A@mail.gmail.com' \
--to=roland@kernel.org \
--cc=bvanassche@acm.org \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=nab@linux-iscsi.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;
as well as URLs for NNTP newsgroup(s).