From: "George Iosif" <giosif@ase.ro>
To: babydr@baby-dragons.com, neilb@suse.de
Cc: linux-raid@vger.kernel.org
Subject: Re: [PATCH md 000 of 8] Introduction
Date: Mon, 17 Oct 2005 13:17:23 +0300 [thread overview]
Message-ID: <s353a474.074@nsa.ase.ro> (raw)
Hello Neil,
If JimL doesn't want/have the time/etc. to do the patch testing I'd be
willing to do that.
Also, if there is something else I could contribute to, I'll be happy to
do it, given I have time for it (I'm employed so I'll try to do it in my
spare time).
Yours,
George Iosif
>>> Neil Brown <neilb@suse.de> 10/17/05 4:38 AM >>>
On Sunday October 16, babydr@baby-dragons.com wrote:
> Hello Neil , Is it possible to inert in the 'Introduction's for
your
> patches a Min & Max kernel level they will successfully patch
> against ? ie: 2.6.12 to 2.6.14-rc4 or some such .
> That would sure take the angst out of guessing . Tia , JimL
>
I could certainly be more precise about which kernel they are created
against (it is usually the latest 2.6-mm) but it would be a lot of
work to figure out how far back you can safely go and still have the
patch usefully apply, and I'm not sure that it is really worth it, is
it?
If you want to help test raid patch (and I do appreciate the help), it
is really best if you use the most recent kernel, otherwise there
could be unexpected interactions which invalidate the test.
Hope that's ok,
Thanks,
NeilBrown
-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2005-10-17 10:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-17 10:17 George Iosif [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-10-14 2:25 [PATCH md 000 of 8] Introduction NeilBrown
2005-10-16 15:57 ` Mr. James W. Laferriere
2005-10-17 2:38 ` Neil Brown
2005-10-18 1:02 ` Mr. James W. Laferriere
2005-08-22 1:59 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=s353a474.074@nsa.ase.ro \
--to=giosif@ase.ro \
--cc=babydr@baby-dragons.com \
--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).