From: NeilBrown <neilb@cse.unsw.edu.au>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-raid@vger.kernel.org
Subject: [PATCH] md - 4 of 10 - Fix typo in comment
Date: Fri, 16 Jan 2004 12:19:38 +1100 [thread overview]
Message-ID: <E1AhIeA-0002UK-00@notabene> (raw)
Thanks dann frazier <dannf@hp.com>
----------- Diffstat output ------------
./include/linux/raid/raid5.h | 2 +-
1 files changed, 1 insertion(+), 1 deletion(-)
diff ./include/linux/raid/raid5.h~current~ ./include/linux/raid/raid5.h
--- ./include/linux/raid/raid5.h~current~ 2004-01-16 11:58:50.000000000 +1100
+++ ./include/linux/raid/raid5.h 2004-01-16 12:00:00.000000000 +1100
@@ -70,7 +70,7 @@
* that the Uptodate bit is set. Once they have checked that they may
* take buffers off the read queue.
*
- * When a buffer on the write list is committed for write is it copied
+ * When a buffer on the write list is committed for write it is copied
* into the cache buffer, which is then marked dirty, and moved onto a
* third list, the written list (bh_written). Once both the parity
* block and the cached buffer are successfully written, any buffer on
reply other threads:[~2004-01-16 1:19 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=E1AhIeA-0002UK-00@notabene \
--to=neilb@cse.unsw.edu.au \
--cc=akpm@osdl.org \
--cc=linux-raid@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