From: "Nicholas A. Bellinger" <nab@linux-iscsi•org>
To: Joe Perches <joe@perches•com>
Cc: linux-scsi <linux-scsi@vger•kernel.org>,
linux-kernel <linux-kernel@vger•kernel.org>,
linux-next <linux-next@vger•kernel.org>,
Randy Dunlap <randy.dunlap@oracle•com>,
Stephen Rothwell <sfr@canb•auug.org.au>,
James Bottomley <James.Bottomley@HansenPartnership•com>
Subject: Re: [PATCH-v2] MAINTAINERS: Add drivers/target/ entry
Date: Mon, 23 May 2011 23:11:09 -0700 [thread overview]
Message-ID: <1306217469.29724.150.camel@haakon2.linux-iscsi.org> (raw)
In-Reply-To: <1306193789.8687.61.camel@Joe-Laptop>
On Mon, 2011-05-23 at 16:36 -0700, Joe Perches wrote:
> On Mon, 2011-05-23 at 14:10 -0700, Nicholas A. Bellinger wrote:
> > From: Nicholas Bellinger <nab@linux-iscsi•org>
> > +TARGET SUBSYSTEM
> > +M: Nicholas A. Bellinger <nab@linux-iscsi•org>
> > +L: linux-scsi@vger•kernel.org
> > +L: http://groups.google.com/group/linux-iscsi-target-dev
> > +W: http://www.linux-iscsi.org
> > +T: git git://git.kernel.org/pub/scm/linux/kernel/git/nab/lio-core-2.6.git master
> > +S: Supported
> > +F: drivers/target/
> > +F: include/target/
> > +F: Documentation/target/
>
> Shouldn't the file layout be more like
>
> drivers/lio/target?
>
Hi Joe,
Not sure what you mean here.. Currently drivers/target/ contains the
fabric independent target core, and /drivers/target/$FABRIC/ contains
individual fabric module drivers.
I originally decided to use drivers/target/ to avoid any confusion wrt
to the 'LIO' term, which to some folks is interchangable wrt to the
'iscsi-target' fabric module.
--nab
next prev parent reply other threads:[~2011-05-24 6:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-23 21:10 [PATCH-v2] MAINTAINERS: Add drivers/target/ entry Nicholas A. Bellinger
2011-05-23 21:13 ` Randy Dunlap
2011-05-23 23:36 ` Joe Perches
2011-05-24 6:11 ` Nicholas A. Bellinger [this message]
2011-05-24 6:43 ` Joe Perches
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=1306217469.29724.150.camel@haakon2.linux-iscsi.org \
--to=nab@linux-iscsi$(echo .)org \
--cc=James.Bottomley@HansenPartnership$(echo .)com \
--cc=joe@perches$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=linux-scsi@vger$(echo .)kernel.org \
--cc=randy.dunlap@oracle$(echo .)com \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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