From: Bart Van Assche <bvanassche@acm.org>
To: linux-scsi@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@suse.de>,
Vladislav Bolkhovitin <vst@vlnb.net>,
Richard Sharpe <realrichardsharpe@gmail.com>
Subject: [PATCHv2 0/3] Move SCST sysfs documentation to Documentation/ABI
Date: Thu, 23 Dec 2010 19:56:54 +0100 [thread overview]
Message-ID: <201012231956.54825.bvanassche@acm.org> (raw)
Since documentation of sysfs attributes must reside in Documentation/ABI, this
series of three patches moves the documentation of the SCST sysfs attributes
to that location. Please review.
Changes since the patch set posted yesterday:
- Removed kernel version.
- All indentation is now done via tabs.
- Changed the contents of the contact field from a mailing list into the name of a person.
- Removed more redundant documentation.
next reply other threads:[~2010-12-23 18:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-23 18:56 Bart Van Assche [this message]
2010-12-23 18:57 ` [PATCHv2 1/3] [SCSI] scst: Move target docs to Documentation/ABI Bart Van Assche
2010-12-23 18:58 ` [PATCHv2 2/3] [SCSI] scst: Move device " Bart Van Assche
2010-12-23 18:58 ` [PATCHv2 3/3] [SCSI] scst: Move devices doc " 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=201012231956.54825.bvanassche@acm.org \
--to=bvanassche@acm.org \
--cc=gregkh@suse.de \
--cc=linux-scsi@vger.kernel.org \
--cc=realrichardsharpe@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).