From: Andrew Morton <akpm@osdl.org>
To: NeilBrown <neilb@suse.de>
Cc: linux-raid@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 000 of 4] md: Introduction
Date: Thu, 24 Aug 2006 15:09:00 -0700 [thread overview]
Message-ID: <20060824150900.36bd9285.akpm@osdl.org> (raw)
In-Reply-To: <20060824173647.19026.patches@notabene>
On Thu, 24 Aug 2006 17:40:56 +1000
NeilBrown <neilb@suse.de> wrote:
>
> Following are 4 patches against 2.6.18-rc4-mm2
>
> The first 2 are bug fixes which should go in 2.6.18, and apply
> equally well to that tree as to -mm.
>
> The latter two should stay in -mm until after 2.6.18.
>
> The second patch is maybe bigger than it absolutely needs to be as a bugfix.
> If you like I can stripe out all the rcu-extra-carefulness as a separate
> patch and just leave the important bit which involves moving the
> atomic_add down twenty-something lines.
>
> Thanks,
> NeilBrown
>
> [PATCH 001 of 4] md: Fix recent breakage of md/raid1 array checking
> [PATCH 002 of 4] md: Fix issues with referencing rdev in md/raid1.
> [PATCH 003 of 4] md: new sysfs interface for setting bits in the write-intent-bitmap
> [PATCH 004 of 4] md: Remove unnecessary variable x in stripe_to_pdidx().
The second patch is against -mm and doesn't come within a mile of applying
to mainline.
next prev parent reply other threads:[~2006-08-24 22:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-24 7:40 NeilBrown
2006-08-24 7:41 ` [PATCH 001 of 4] md: Fix recent breakage of md/raid1 array checking NeilBrown
2006-08-24 7:41 ` [PATCH 002 of 4] md: Fix issues with referencing rdev in md/raid1 NeilBrown
2006-08-24 7:41 ` [PATCH 003 of 4] md: new sysfs interface for setting bits in the write-intent-bitmap NeilBrown
2006-08-24 7:41 ` [PATCH 004 of 4] md: Remove unnecessary variable x in stripe_to_pdidx() NeilBrown
2006-08-24 22:09 ` Andrew Morton [this message]
2006-08-25 8:06 ` [PATCH 000 of 4] md: Introduction Neil Brown
2006-08-29 5:39 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=20060824150900.36bd9285.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
/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
Powered by JetHome