All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@suse.de>
To: Bart Van Assche <bvanassche@acm.org>
Cc: linux-scsi@vger.kernel.org, vst@vlnb.net,
	realrichardsharpe@gmail.com, scst-devel@lists.sourceforge.net
Subject: Re: [PATCH 2/3] [SCSI] scst: Move SCST device documentation to Documentation/ABI
Date: Wed, 22 Dec 2010 16:20:53 -0800	[thread overview]
Message-ID: <20101223002053.GA7475@suse.de> (raw)
In-Reply-To: <201012222146.28782.bvanassche@acm.org>

On Wed, Dec 22, 2010 at 09:46:28PM +0100, Bart Van Assche wrote:
> Move the documentation about the sysfs attributes of the SCST
> virtual device to Documentation/ABI/stable.
> 
> Signed-off-by: Bart Van Assche <bvanassche@acm.org>
> Cc: Greg Kroah-Hartman <gregkh@suse.de>
> Cc: Vladislav Bolkhovitin <vst@vlnb.net>
> ---
>  Documentation/ABI/stable/sysfs-devices-scst |  150 +++++++++++++++++++++++++++
>  Documentation/scst/README.scst              |   71 -------------
>  2 files changed, 150 insertions(+), 71 deletions(-)
>  create mode 100644 Documentation/ABI/stable/sysfs-devices-scst
> 
> diff --git a/Documentation/ABI/stable/sysfs-devices-scst b/Documentation/ABI/stable/sysfs-devices-scst
> new file mode 100644
> index 0000000..80bc258
> --- /dev/null
> +++ b/Documentation/ABI/stable/sysfs-devices-scst
> @@ -0,0 +1,150 @@
> +What:           /sys/devices/scst/mgmt

How did you get a file into this directory?  Are you sure that's
acceptable?  Same for the other files you added here.

> +Date:           December 2010
> +KernelVersion:  2.6.38

Really?  That's pretty presumptious, isn't it?

> +Contact:        linux-scsi@vger.kernel.org

Why not the "owner" of this code, not the scsi mailing list.

> +Description:
> +		Interface through which SCST management commands can be issued.

You mix tabs and spaces above and in all of your other files.  Please
make them only tabs.
> +		The documentation of the syntax of these commands can be
> +		obtained by reading this file:
> +
> +		# cat mgmt
> +		in device/<dev> <dev_cmd>
> +		in device_driver/<devt> <devt_cmd>
> +		in target_driver/<tgtt> <tgtt_cmd>
> +		in target_driver/<tgtt>/<target>/luns <tgt_cmd>
> +		in target_driver/<tgtt>/<target>/luns <luns_cmd>
> +		in target_driver/<tgtt>/<target>/ini_groups <acg_mgmt_cmd>
> +		in target_driver/<tgtt>/<target>/ini_groups/<acg> <acg_cmd>
> +		in target_driver/<tgtt>/<target>/ini_groups/<acg>/luns <luns_cmd>
> +		in target_driver/<tgtt>/<target>/ini_groups/<acg>/initiators <acg_ini_cmd>

What?  sysfs is one value per file, why would the mgmt file return more
than one line?  That's not acceptable, sorry.

> +
> +		dev_cmd syntax:
> +
> +		set_filename <filename>
> +		set_threads_num <n>
> +		set_thread_pool_type <thread_pool_type>
> +
> +		devt_cmd syntax:
> +
> +		add_device device_name [parameters]
> +		del_device device_name
> +		add_attribute <attribute> <value>
> +		del_attribute <attribute> <value>
> +		add_device_attribute device_name <attribute> <value>
> +		del_device_attribute device_name <attribute> <value>
> +
> +		devt_cmd syntax for pass-through device types:
> +
> +		add_device H:C:I:L
> +		del_device H:C:I:L
> +
> +		tgtt_cmd syntax:
> +
> +		add_target target_name [parameters]
> +		del_target target_name
> +		add_attribute <attribute> <value>
> +		del_attribute <attribute> <value>
> +		add_target_attribute target_name <attribute> <value>"
> +		del_target_attribute target_name <attribute> <value>"
> +
> +		where parameters is one or more <name>=<value> pairs separated by ';'
> +
> +		tgt_cmd syntax:
> +
> +		enable
> +		disable
> +		set_cpu_mask <mask>
> +
> +		luns_cmd syntax:
> +
> +		add|del H:C:I:L lun [parameters]
> +		add VNAME lun [parameters]
> +		del lun
> +		replace H:C:I:L lun [parameters]
> +		replace VNAME lun [parameters]
> +		clear
> +
> +		where parameters is either 'read_only' or empty.
> +
> +		acg_mgmt_cmd syntax:
> +
> +		create <group_name>
> +		del <group_name>
> +
> +		acg_cmd syntax:
> +		set_cpu_mask <mask>
> +
> +		acg_ini_cmd syntax:
> +
> +		add <initiator_name>
> +		del <initiator_name>
> +		move <initiator_name> <dest_group_name>
> +		clear

That's quite complex, are you sure it's correct, and actually describes
it in a manner that anyone else can use?

Again, one value per file.

thanks,

greg k-h

  reply	other threads:[~2010-12-23  0:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-22 20:44 [PATCH 0/3] Move SCST sysfs documentation to Documentation/ABI Bart Van Assche
2010-12-22 20:45 ` [PATCH 1/3] [SCSI] scst: Move target " Bart Van Assche
2010-12-22 20:46 ` [PATCH 2/3] [SCSI] scst: Move SCST device " Bart Van Assche
2010-12-23  0:20   ` Greg KH [this message]
2010-12-23 11:33     ` Bart Van Assche
2010-12-22 20:47 ` [PATCH 3/3] [SCSI] scst: Move SCST devices " Bart Van Assche
2010-12-23 15:11   ` Konrad Rzeszutek Wilk
2010-12-24 12:01     ` Bart Van Assche

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=20101223002053.GA7475@suse.de \
    --to=gregkh@suse.de \
    --cc=bvanassche@acm.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=realrichardsharpe@gmail.com \
    --cc=scst-devel@lists.sourceforge.net \
    --cc=vst@vlnb.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.