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

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <46D459C9.9050709@oracle.com>
Date:	Tue, 28 Aug 2007 10:22:17 -0700
From:	Randy Dunlap <randy.dunlap@...cle.com>
To:	Michael Evans <mjevans1983@...il.com>
CC:	Bill Davidsen <davidsen@....com>,
	"Michael J. Evans" <mjevans1983@...cast.net>,
	Neil Brown <neilb@...e.de>, Ingo Molnar <mingo@...hat.com>,
	linux-raid@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [patch v3 1/1] md: Software Raid autodetect dev list not array

Michael Evans wrote:
> On 8/28/07, Randy Dunlap <randy.dunlap@...cle.com> wrote:
>> Michael Evans wrote:
>>> On 8/28/07, Bill Davidsen <davidsen@....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@...ux-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 ***
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/