Re: [patch v3 1/1] md: Software Raid autodetect dev list not array

["Michael Evans" <mjevans1983@gmail.com>]

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,)

> Mainline progresses (roughly, e.g.) like so:
>

I knew about the progression order (but not timing) of the non-git
side of it, but it was helpful to have the whole thing spelled out,
thank you.