From: Jeff Breidenbach <jeff@jab.org>
To: NeilBrown <neilb@suse.de>
Cc: linux-raid@vger.kernel.org
Subject: Recommended kernel?
Date: Sun, 27 Aug 2006 17:06:50 -0700 [thread overview]
Message-ID: <1156723613.27EF420C@dk12.dngr.org> (raw)
In-Reply-To: <20060828092849.21292.patches@notabene>
I'm thinking about upgrading from Linux 2.6.14 to some newer kernel -
probably to whatever is in Debian unstable. They're all basically safe
for md and RAID1, right? No gotcha kernel versions to especially avoid?
--Jeff
next prev parent reply other threads:[~2006-08-28 0:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-27 23:49 [PATCH 000 of 4] md: Introduction - some revised/reordered patches NeilBrown
2006-08-27 23:49 ` [PATCH 001 of 4] md: Fix issues with referencing rdev in md/raid1 NeilBrown
2006-08-27 23:49 ` [PATCH 002 of 4] md: Factor out part of raid1d into a separate function NeilBrown
2006-08-27 23:49 ` [PATCH 003 of 4] md: Remove working_disks from raid1 state data NeilBrown
2006-08-27 23:49 ` [PATCH 004 of 4] md: Improve locking around error handling NeilBrown
2006-08-28 0:06 ` Jeff Breidenbach [this message]
2006-08-28 0:11 ` Recommended kernel? Neil Brown
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=1156723613.27EF420C@dk12.dngr.org \
--to=jeff@jab.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;
as well as URLs for NNTP newsgroup(s).