From: Andi Kleen <andi@halobates.de>
To: Kent Overstreet <kent.overstreet@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] Bcache: version 4
Date: Tue, 04 May 2010 12:14:03 +0200 [thread overview]
Message-ID: <87y6g03rf8.fsf@basil.nowhere.org> (raw)
In-Reply-To: <20100501001212.GA31135@moria> (Kent Overstreet's message of "Fri, 30 Apr 2010 16:12:13 -0800")
Kent Overstreet <kent.overstreet@gmail.com> writes:
> I've got some documentation incorporated since the last posting. The
> user documentation should be sufficient; the code could probably use
> more but it's hard for me to say what, so I'll try and add whatever
> people find unclear.
I read all of this email now and I still have no clue what exactly
a 'bcache' is and why anyone would want one (and if one needs
a large stick to handle it or not)
Normally the 0/x series of a patch kit is supposed to contain that
information.
I know it's probably obvious to you, but it's not to most other readers.
Consider adding some introduction?
-Andi
--
ak@linux.intel.com -- Speaking for myself only.
next prev parent reply other threads:[~2010-05-04 10:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-01 0:12 [PATCH 0/3] Bcache: version 4 Kent Overstreet
2010-05-01 13:01 ` Valdis.Kletnieks
2010-05-01 18:43 ` Kent Overstreet
2010-05-04 10:14 ` Andi Kleen [this message]
2010-05-04 23:47 ` Kent Overstreet
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=87y6g03rf8.fsf@basil.nowhere.org \
--to=andi@halobates.de \
--cc=kent.overstreet@gmail.com \
--cc=linux-kernel@vger.kernel.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