All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrik Jonsson <patrik@ucolick.org>
Cc: linux-raid@vger.kernel.org
Subject: Kernels and MD versions (was: md: Introduction - raid5 reshape mark-2)
Date: Wed, 08 Feb 2006 22:35:05 -0800	[thread overview]
Message-ID: <43EAE299.9000508@ucolick.org> (raw)
In-Reply-To: <17386.47069.138562.339803@cse.unsw.edu.au>

[-- Attachment #1: Type: text/plain, Size: 1550 bytes --]

Neil Brown wrote:
> I always make them against the latest -mm kernel, so that would be a
> good place to start.  However things change quickly and I can't
> promise it will apply against whatever is the 'latest' today.
> 
> If you would like to nominate a particular recent kernel, I'll create
> a patch set that is guaranteed to apply against that. (Testing is
> always appreciated, and well worth that small effort on my part).

I find this is a major problem for me, too. Even though I try to stay up
to date with the md developments, I have a hard time piecing together
which past patches went with which version, so if I get a recent version
I don't know which patches need to be applied and which are already in
there.

My suggestion is that Neil, should he be willing, keep a log somewhere
which detail kernel version and what major updates in md functionality
go along with it. Something like
2.6.14         raid5 read error correction
2.6.15         md /sys interface
2.6.16.rc1     raid5 reshape
2.6.16.rc2-mm4 something else cool

it would include the released kernels and the previews of the current
kernel. That way, say I see that the latest FC4 kernel is 2.6.14, I
could look and see that since the raid5 read error correction was
included, I don't have to go looking for the patches.

Maybe this is too much hassle (or maybe it's already out there
somewhere) but I'm thinking simple, and I think it would give a
high-level overview of the development for us who are not intimately
involved in every kernel version.

Regards,

/Patrik

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 254 bytes --]

  reply	other threads:[~2006-02-09  6:35 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-24  0:40 [PATCH 000 of 7] md: Introduction - raid5 reshape mark-2 NeilBrown
2006-01-24  0:40 ` [PATCH 001 of 7] md: Split disks array out of raid5 conf structure so it is easier to grow NeilBrown
2006-01-24  0:40 ` [PATCH 002 of 7] md: Allow stripes to be expanded in preparation for expanding an array NeilBrown
2006-01-24  0:41 ` [PATCH 003 of 7] md: Infrastructure to allow normal IO to continue while array is expanding NeilBrown
2006-01-24  0:41 ` [PATCH 004 of 7] md: Core of raid5 resize process NeilBrown
2006-01-24  0:41 ` [PATCH 005 of 7] md: Final stages of raid5 expand code NeilBrown
2006-01-24  0:41 ` [PATCH 006 of 7] md: Checkpoint and allow restart of raid5 reshape NeilBrown
2006-01-27 12:37   ` Molle Bestefich
2006-01-24  0:41 ` [PATCH 007 of 7] md: Only checkpoint expansion progress occasionally NeilBrown
2006-01-24  9:23 ` [PATCH 000 of 7] md: Introduction - raid5 reshape mark-2 Lars Marowsky-Bree
2006-01-24  9:23   ` Lars Marowsky-Bree
2006-01-24  9:32   ` Neil Brown
2006-02-07 17:13 ` Henrik Holst
2006-02-09  3:32   ` Neil Brown
2006-02-09  6:35     ` Patrik Jonsson [this message]
2006-02-09 18:07       ` Kernels and MD versions (was: md: Introduction - raid5 reshape mark-2) Mr. James W. Laferriere

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=43EAE299.9000508@ucolick.org \
    --to=patrik@ucolick.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.