From: "Nicholas A. Bellinger" <nab@linux-iscsi.org>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: linux-scsi <linux-scsi@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Christoph Hellwig <hch@lst.de>,
Mike Christie <michaelc@cs.wisc.edu>,
Hannes Reinecke <hare@suse.de>,
FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>,
Joel Becker <jlbec@evilplan.org>,
Douglas Gilbert <dgilbert@interlog.com>
Subject: Re: [PATCH 0/5] target updates for scsi-post-merge .39 (round one, v2)
Date: Mon, 28 Feb 2011 16:33:05 -0800 [thread overview]
Message-ID: <1298939585.5401.270.camel@haakon2.linux-iscsi.org> (raw)
In-Reply-To: <1298938784.2487.72.camel@mulgrave.site>
On Mon, 2011-02-28 at 18:19 -0600, James Bottomley wrote:
> On Mon, 2011-02-28 at 16:17 -0800, Nicholas A. Bellinger wrote:
> > From: Nicholas Bellinger <nab@linux-iscsi.org>
> >
> > Hi James and Co,
> >
> > The following is the first round (v2) of target patches intended for .39
> > scsi-post-merge tree that introduces new target functionality and the
> > first mainline TCM fabric module (TCM_Loop).
>
> OK, what postmerge tree? There haven't been any conflicts this merge
> cycle that necessitate running one. Do you mean you want these after
> the merge window for some reason?
>
Not really. What I meant here is that this series needs to be applied
after the original 14 part series 'for .39 scsi-misc' fixes held over
for .38..
I was not sure if scsi-misc was for fixes only now, and if new target
code (like this series) should be going into scsi-post-merge or what..
So it sounds like this series for configfs statistics infrastructure and
initial TCM_Loop merge should be going through scsi-misc as well for
mainline .39, yes..?
Also, just another heads up in TCM fabric module land. At this point in
lio-core-2.6.git/lio-4.1, drivers/target/iscsi/ has been fully converted
to use mainline libiscsi -> include/scsi/iscsi_proto.h definitions with
a few small additions/corrections. This also includes a new set of
iSCSI fabric dependent ConfigFS statistics groups, and include the
removal of legacy ProcFS code from iscsi_target_mod.
The full iscsi_target_mod series will be posted in the next days for
review and comments.
Best Regards,
--nab
prev parent reply other threads:[~2011-03-01 0:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-01 0:17 Nicholas A. Bellinger
2011-03-01 0:17 ` [PATCH 1/5] target: add initial device backend context target_core_stat.c code Nicholas A. Bellinger
2011-03-01 0:17 ` [PATCH 2/5] target: add initial fabric port " Nicholas A. Bellinger
2011-03-01 0:17 ` [PATCH 3/5] target: add initial fabric MappedLUN " Nicholas A. Bellinger
2011-03-01 0:17 ` [PATCH 4/5] target: Add fabric_stat_group for fabric module statistics default_group Nicholas A. Bellinger
2011-03-01 0:17 ` [PATCH 5/5] tcm_loop: Add multi-fabric Linux/SCSI LLD fabric module Nicholas A. Bellinger
2011-03-01 0:19 ` [PATCH 0/5] target updates for scsi-post-merge .39 (round one, v2) James Bottomley
2011-03-01 0:33 ` Nicholas A. Bellinger [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=1298939585.5401.270.camel@haakon2.linux-iscsi.org \
--to=nab@linux-iscsi.org \
--cc=James.Bottomley@HansenPartnership.com \
--cc=dgilbert@interlog.com \
--cc=fujita.tomonori@lab.ntt.co.jp \
--cc=hare@suse.de \
--cc=hch@lst.de \
--cc=jlbec@evilplan.org \
--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 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®