From: Andrew Morton <akpm@osdl.org>
To: NeilBrown <neilb@cse.unsw.edu.au>
Cc: linux-raid@vger.kernel.org
Subject: Re: [PATCH md 0 of 4] Introduction
Date: Mon, 7 Mar 2005 22:10:06 -0800 [thread overview]
Message-ID: <20050307221006.16806431.akpm@osdl.org> (raw)
In-Reply-To: <20050308165021.3745.patches@notabene>
NeilBrown <neilb@cse.unsw.edu.au> wrote:
>
> The first two are trivial and should apply equally to 2.6.11
>
> The second two fix bugs that were introduced by the recent
> bitmap-based-intent-logging patches and so are not relevant
> to 2.6.11 yet.
The changelog for the "Fix typo in super_1_sync" patch doesn't actually say
what the patch does. What are the user-visible consequences of not fixing
this?
Is the bitmap stuff now ready for Linus?
next prev parent reply other threads:[~2005-03-08 6:10 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-08 5:50 [PATCH md 0 of 4] Introduction NeilBrown
2005-03-08 5:50 ` [PATCH md 3 of 4] Initialise sync_blocks in raid1 resync NeilBrown
2005-03-08 5:50 ` [PATCH md 1 of 4] Fix typo in super_1_sync NeilBrown
2005-03-08 5:50 ` [PATCH md 2 of 4] Erroneous sizeof use in raid1 NeilBrown
2005-03-08 5:50 ` [PATCH md 4 of 4] Fix md deadlock due to md thread processing delayed requests NeilBrown
2005-03-08 6:10 ` Andrew Morton [this message]
2005-03-09 3:17 ` [PATCH md 0 of 4] Introduction Neil Brown
2005-03-09 9:27 ` Mike Tran
2005-03-08 12:49 ` Peter T. Breuer
2005-03-08 17:02 ` Paul Clements
2005-03-08 19:05 ` Peter T. Breuer
2005-03-09 5:07 ` Neil Brown
2005-03-09 15:37 ` Peter T. Breuer
-- strict thread matches above, loose matches on Subject: below --
2004-11-02 3:37 NeilBrown
2004-09-03 2:20 NeilBrown
2004-08-23 3:10 NeilBrown
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=20050307221006.16806431.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@cse.unsw.edu.au \
/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).