From mboxrd@z Thu Jan 1 00:00:00 1970 From: Patrik Jonsson Subject: Kernels and MD versions (was: md: Introduction - raid5 reshape mark-2) Date: Wed, 08 Feb 2006 22:35:05 -0800 Message-ID: <43EAE299.9000508@ucolick.org> References: <20060124112626.4447.patches@notabene> <43E8D53E.4010202@idgmail.se> <17386.47069.138562.339803@cse.unsw.edu.au> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigEA77711232BA9EEBCACA208D" Return-path: In-Reply-To: <17386.47069.138562.339803@cse.unsw.edu.au> Sender: linux-raid-owner@vger.kernel.org Cc: linux-raid@vger.kernel.org List-Id: linux-raid.ids This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigEA77711232BA9EEBCACA208D Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit 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 --------------enigEA77711232BA9EEBCACA208D Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (MingW32) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFD6uKZT+KvsdUW5p8RArW/AJ9O/WBQfZI11V/mEd2Mog/CKk8v0wCgp3cK BsrYZsHZ2GXcAyI3xzTKbDM= =h+8v -----END PGP SIGNATURE----- --------------enigEA77711232BA9EEBCACA208D--