From: Randy Dunlap <randy.dunlap@oracle.com>
To: Michael Evans <mjevans1983@gmail.com>
Cc: Bill Davidsen <davidsen@tmr.com>,
"Michael J. Evans" <mjevans1983@comcast.net>,
Neil Brown <neilb@suse.de>, Ingo Molnar <mingo@redhat.com>,
linux-raid@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [patch v3 1/1] md: Software Raid autodetect dev list not array
Date: Tue, 28 Aug 2007 10:22:17 -0700 [thread overview]
Message-ID: <46D459C9.9050709@oracle.com> (raw)
In-Reply-To: <4877c76c0708281010x4597a9cfpc252dc4ee2a0ef9e@mail.gmail.com>
Michael Evans wrote:
> On 8/28/07, Randy Dunlap <randy.dunlap@oracle.com> wrote:
>> Michael Evans wrote:
>>> On 8/28/07, Bill Davidsen <davidsen@tmr.com> wrote:
>>>> Michael Evans wrote:
>>>>> Oh, I see. I forgot about the changelogs. I'd send out version 5
>>>>> now, but I'm not sure what kernel version to make the patch against.
>>>>> 2.6.23-rc4 is on kernel.org and I don't see any git snapshots.
>>>>> Additionally I never could tell what git tree was the 'mainline' as it
>>>>> isn't labeled with such a keyword (at least in the list of git trees I
>>>>> saw).
>>>> I suspect you wait for 2.5.23 release, or send it to AKPM for inclusion
>>>> in an "-mm" kernel. That's probably desirable, anyway.
>>>>
>>>> --
>>> There's another list I should CC to? Or does the section maintainer
>>> do that when they're happy with the patch?
>> Not another list; just cc: akpm@linux-foundation.org so that he can merge
>> it into the -mm kernel patches for testing. Most patches cook in the -mm
>> kernel(s) before they are merged into mainline.
>>
>> Then generally the subsystem maintainer(s) are responsible for sending
>> patches on to Linus for merging into mainline, if/when they are happy
>> with the patch and they think that it has been tested enough.
>>
>
> So I should look at the git documentation again, try to pull down
> Andrew's latest -mm, and see what I need to change (if anything) to
> patch against it? (I would probably only verify that boots once my
> self given the other testing this has already seen and how often mm
> breaks things my mythtv box likes, such as nvidia-drivers, etc,)
-mm is available only as a patchset, not via git.
There has been a git version of it, but it's not currently working and
hasn't been for 2 months or so.
I mostly use the grab_kernel script that I mentioned. It knows how
to download linux-2.6.M and how to apply -rcN, -gitN, and/or -mmN
patches to the base (linux-2.6.M).
E.g.:
grab_kernel 2.6.23-rc3-git6 $PWD
or
grab_kernel 2.6.23-rc3-mm1 $PWD
--
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
next prev parent reply other threads:[~2007-08-28 17:23 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200708222058.45480.mjevans1983@comcast.net>
2007-08-24 3:37 ` [patch 1/1] md: Software Raid autodetect dev list not array Neil Brown
2007-08-24 5:50 ` Michael Evans
2007-08-26 11:51 ` [patch v2 " Michael J. Evans
2007-08-26 12:20 ` Michael Evans
2007-08-27 3:41 ` Kyle Moffett
2007-08-27 7:56 ` Michael Evans
2007-08-26 12:56 ` Jan Engelhardt
2007-08-26 15:58 ` Michael Evans
2007-08-26 16:56 ` Randy Dunlap
2007-08-26 19:18 ` Michael Evans
2007-08-27 22:16 ` [patch v3 " Michael J. Evans
2007-08-27 22:30 ` Randy Dunlap
2007-08-28 4:38 ` Michael J. Evans
2007-08-28 4:46 ` Randy Dunlap
2007-08-28 13:08 ` Michael Evans
2007-08-28 13:14 ` Jan Engelhardt
2007-08-28 13:26 ` Michael J. Evans
2007-08-28 13:24 ` Bill Davidsen
2007-08-28 13:32 ` Michael Evans
2007-08-28 16:15 ` Randy Dunlap
2007-08-28 17:10 ` Michael Evans
2007-08-28 17:22 ` Randy Dunlap [this message]
2007-08-28 19:11 ` Michael Evans
2007-08-28 19:16 ` Randy Dunlap
2007-08-29 8:06 ` [patch v5 " Michael J. Evans
2007-08-29 15:18 ` Randy Dunlap
2007-08-28 13:27 ` Michael J. Evans
2007-08-28 4:39 ` [patch v4 " Michael J. Evans
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=46D459C9.9050709@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=davidsen@tmr.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=mjevans1983@comcast.net \
--cc=mjevans1983@gmail.com \
--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 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.