From: NeilBrown <neilb@suse.de>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-raid@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 000 of 2] md: To more bugfixes for 2.6.25
Date: Fri, 7 Mar 2008 16:00:40 +1100 [thread overview]
Message-ID: <20080307155754.25976.patches@notabene> (raw)
Two more little bug fixes for md in 2.6.25.
One fixes a formatting error in /proc/mdstat. Technically this is a
user-interface change for an interface that has been around since
2.6.15. However the only program known to parse this file trips over
the error. So I think it is safe to fix it.
The second fixes a small bug in a recent patch.
[PATCH 001 of 2] md: Fix formatting error in /proc/mdstat.
[PATCH 002 of 2] md: Reduce CPU wastage on idle md array with a write-intent bitmap. fix
next reply other threads:[~2008-03-07 5:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-07 5:00 NeilBrown [this message]
2008-03-07 5:00 ` [PATCH 001 of 2] md: Fix formatting error in /proc/mdstat NeilBrown
2008-03-07 5:00 ` [PATCH 002 of 2] md: Reduce CPU wastage on idle md array with a write-intent bitmap. fix 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=20080307155754.25976.patches@notabene \
--to=neilb@suse.de \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).