public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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 12:16:26 -0700	[thread overview]
Message-ID: <46D4748A.4070909@oracle.com> (raw)
In-Reply-To: <4877c76c0708281211s55aded4ajceb283da25223659@mail.gmail.com>

Michael Evans wrote:
> On 8/28/07, Randy Dunlap <randy.dunlap@oracle.com> wrote:
>> 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.
> 
> Gentoo's mm-sources is version 2.6.23-rc3-mm1, which I'd guess is
> close enough for an area like this.  Given that I didn't need to make
> any changes to the patch should I just submit it to the mm for testing
> without rebooting in to an mm-sources kernel?  I need to schedule when
> I do that so it would take me overnight to do so.

Yes, I think that you can go ahead with that, but it's up to the
subsystem maintainers where/when it goes from there.

-- 
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***

  reply	other threads:[~2007-08-28 19:31 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
2007-08-28 19:11                             ` Michael Evans
2007-08-28 19:16                               ` Randy Dunlap [this message]
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=46D4748A.4070909@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox