From: Andi Kleen <andi@firstfloor.org>
To: "Nicholas A. Bellinger" <nab@linux-iscsi.org>
Cc: James Bottomley <James.Bottomley@suse.de>,
Christoph Hellwig <hch@infradead.org>,
FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>,
Mike Christie <michaelc@cs.wisc.edu>,
Douglas@firstfloor.org, Gilbe@firstfloor.org,
linux-scsi <linux-scsi@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [RFC]: Mainline of TCM Core and TCM_Loop for v2.6.35
Date: Sun, 30 May 2010 11:27:26 +0200 [thread overview]
Message-ID: <87vda5zqm9.fsf@basil.nowhere.org> (raw)
In-Reply-To: <1274317792.30733.59.camel@haakon2.linux-iscsi.org> (Nicholas A. Bellinger's message of "Wed\, 19 May 2010 18\:09\:52 -0700")
"Nicholas A. Bellinger" <nab@linux-iscsi.org> writes:
>
> As always, I am open to constructive suggestions,
Your description contains quite a lot of acronyms (I count 8 in the first
paragraph alone). For the benefit of the linux-kernel audience which are
not storage experts and are struggling to find out what this is all good
for, how about including a glossary that explains what it all means? I
suspect having that in the git commit log later will be also useful.
Thanks,
-Andi
--
ak@linux.intel.com -- Speaking for myself only.
next prev parent reply other threads:[~2010-05-30 9:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-20 1:09 [RFC]: Mainline of TCM Core and TCM_Loop for v2.6.35 Nicholas A. Bellinger
2010-05-27 18:41 ` Vladislav Bolkhovitin
2010-05-28 2:01 ` Nicholas A. Bellinger
2010-05-29 17:26 ` Vladislav Bolkhovitin
2010-05-30 9:27 ` Andi Kleen [this message]
2010-05-31 3:47 ` 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=87vda5zqm9.fsf@basil.nowhere.org \
--to=andi@firstfloor.org \
--cc=Douglas@firstfloor.org \
--cc=Gilbe@firstfloor.org \
--cc=James.Bottomley@suse.de \
--cc=fujita.tomonori@lab.ntt.co.jp \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=michaelc@cs.wisc.edu \
--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