From: Randy Dunlap <randy.dunlap@oracle.com>
To: "Nicholas A. Bellinger" <nab@linux-iscsi.org>
Cc: linux-scsi <linux-scsi@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [RFCv3 20/21] tcm: Add Kbuild and Kconfig for drivers/target and Documentation/target/
Date: Mon, 18 Oct 2010 15:48:59 -0700 [thread overview]
Message-ID: <20101018154859.66b71121.randy.dunlap@oracle.com> (raw)
In-Reply-To: <1287441559-20129-1-git-send-email-nab@linux-iscsi.org>
On Mon, 18 Oct 2010 15:39:19 -0700 Nicholas A. Bellinger wrote:
> From: Nicholas Bellinger <nab@linux-iscsi.org>
>
> Add TCM Kbuild and Kconfig files and update drivers/ to pick up drivers/target.
> Add Docmentation/target/ for tcm_mod_builder.py script for generating new
> TCM v4 fabric modules functional ConfigFS skeletons.
>
> Signed-off-by: Nicholas A. Bellinger <nab@linux-iscsi.org>
> ---
> Documentation/target/tcm_mod_builder.py | 1094 ++++++++++++++++++++++++++++++
> Documentation/target/tcm_mod_builder.txt | 145 ++++
> drivers/Kconfig | 2 +
> drivers/Makefile | 1 +
> drivers/target/Kbuild | 27 +
> drivers/target/Kconfig | 34 +
> 6 files changed, 1303 insertions(+), 0 deletions(-)
> create mode 100755 Documentation/target/tcm_mod_builder.py
> create mode 100644 Documentation/target/tcm_mod_builder.txt
> create mode 100644 drivers/target/Kbuild
> create mode 100644 drivers/target/Kconfig
> diff --git a/drivers/target/Kconfig b/drivers/target/Kconfig
> new file mode 100644
> index 0000000..5c37653
> --- /dev/null
> +++ b/drivers/target/Kconfig
> @@ -0,0 +1,34 @@
> +config TARGET_CORE
> + tristate "Generic Target Core Mod (TCM) and ConfigFS Infrastructure"
> + select CONFIGFS_FS
Indentation: use tabs, not spaces.
> + default m
Don't enable random drivers/modules.
Let the user or defconfig do that.
> + ---help---
> + Say Y or M here to enable the TCM Storage Engine and ConfigFS enabled control path for target_core_mod. This includes built-in TCM RAMDISK subsystem logic for virtual LUN 0 access
> +
> +config TCM_DEBUG_DEV
> + tristate "TCM Debug device code"
> + depends on TARGET_CORE
> + default n
> + ---help---
> + Say Y here to enable the TCM Debug device code
> +
> +config TCM_IBLOCK
> + tristate "TCM/IBLOCK Subsystem Plugin for Linux/BLOCK"
> + depends on TARGET_CORE
> + default y
> + ---help---
> + Say Y here to enable the TCM/IBLOCK subsystem plugin for non-buffered access to Linux/Block devices using BIO
> +
> +config TCM_FILEIO
> + tristate "TCM/FILEIO Subsystem Plugin for Linux/VFS"
> + depends on TARGET_CORE
> + default y
> + ---help---
> + Say Y here to enable the TCM/FILEIO subsystem plugin for buffered access to Linux/VFS struct file or struct block_device
> +
> +config TCM_PSCSI
> + tristate "TCM/pSCSI Subsystem Plugin for Linux/SCSI"
> + depends on TARGET_CORE
> + default y
> + ---help---
> + Say Y here to enable the TCM/pSCSI subsystem plugin for non-buffered passthrough access to Linux/SCSI device
> --
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
next prev parent reply other threads:[~2010-10-18 22:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-18 22:39 Nicholas A. Bellinger
2010-10-18 22:48 ` Randy Dunlap [this message]
2010-10-18 23:03 ` Nicholas A. Bellinger
2010-10-18 22:54 ` Randy Dunlap
2010-10-18 23:16 ` 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=20101018154859.66b71121.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=nab@linux-iscsi.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®