From: "Nicholas A. Bellinger" <nab@linux-iscsi.org>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Christoph Hellwig <hch@lst.de>,
Mike Christie <michaelc@cs.wisc.edu>,
FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>,
Stephen Rothwell <sfr@canb.auug.org.au>,
linux-scsi <linux-scsi@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL for 38-rc3] target updates for v4.0.0-rc7
Date: Mon, 24 Jan 2011 17:27:51 -0800 [thread overview]
Message-ID: <1295918871.24778.161.camel@haakon2.linux-iscsi.org> (raw)
In-Reply-To: <1295915790.15425.44.camel@mulgrave.site>
On Mon, 2011-01-24 at 18:36 -0600, James Bottomley wrote:
> On Mon, 2011-01-24 at 16:14 -0800, Nicholas A. Bellinger wrote:
> > Hi James and Co,
> >
> > Here are the latest v4.0.0-rc7 updates for mainline drivers/target/ code
> > rebased against linux-2.6.git -> .38-rc2. These individual patches have
> > been reviewed on linux-scsi and commited into the upstream LIO kernel
> > tree, so please consider pulling for .38-rc3:
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/nab/scsi-post-merge-2.6.git for-38-rc3
> >
> > Also at this point, having Linus pull directly from
> > scsi-post-merge-2.6.git/for-38-rcX for mainline target bugfixes +
> > improvements may make more sense.
> >
> > Linus/Andrew/James, please let me know which you prefer here.
>
> Right at the moment, I'm trying to encourage a few people with
> established areas to experiment with their own git trees in SCSI, but
> the target subsystem, being a newcomer, wouldn't be one of these, so,
> for the time being, patch series over linux-scsi please for review and
> feedback.
>
Sure, thanks for the clarification. The same set of patches are
available against your .37-FINAL based scsi-post-merge-2.6.git/master
HEAD here:
git://git.kernel.org/pub/scm/linux/kernel/git/nab/scsi-post-merge-2.6.git for-jejb
Please let me know if you have any further questions,
--nab
next prev parent reply other threads:[~2011-01-25 1:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-25 0:14 Nicholas A. Bellinger
2011-01-25 0:36 ` James Bottomley
2011-01-25 1:27 ` Nicholas A. Bellinger [this message]
2011-01-25 1:38 ` James Bottomley
2011-01-25 1:55 ` Nicholas A. Bellinger
2011-01-25 2:26 ` James Bottomley
2011-01-25 2:48 ` 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=1295918871.24778.161.camel@haakon2.linux-iscsi.org \
--to=nab@linux-iscsi.org \
--cc=James.Bottomley@HansenPartnership.com \
--cc=akpm@linux-foundation.org \
--cc=fujita.tomonori@lab.ntt.co.jp \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=michaelc@cs.wisc.edu \
--cc=sfr@canb.auug.org.au \
--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®