public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bill Gatliff <bgat@billgatliff.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Kevin Hilman <khilman@deeprootsystems.com>,
	linux-arm-kernel@lists.infradead.org,
	Tony Lindgren <tony@atomide.com>,
	linux-kernel@vger.kernel.org, linux-arm@vger.kernel.org,
	Alan Cox <alan@lxorguk.ukuu.org.uk>, Nicolas Pitre <nico@cam.org>,
	Russell King <rmk@arm.linux.org.uk>
Subject: Re: ARM subarch submissions for next merge window
Date: Tue, 25 Aug 2009 14:48:58 -0500	[thread overview]
Message-ID: <4A94402A.1090003@billgatliff.com> (raw)
In-Reply-To: <alpine.LFD.2.01.0908241249200.3158@localhost.localdomain>

Linus Torvalds wrote:
> On Mon, 24 Aug 2009, Kevin Hilman wrote:
>   
>> After some discussions on linux-arm-kernel during the last merge
>> window, a suggestion from Alan Cox[1], and a willingness to try it
>> from Russell[2], some ARM subarch maintainers would like to push our
>> platform-specific code directly to you for the next merge window.
>>     

How do you define "subarch maintainer"?  If I have a new platform port, 
but am heretofore unknown to linux-arm-kernel, do I still send a pull 
request to Linus directly?  Or are the subarch maintainers the guys like 
Russell, Nico, Tony, etc. and _they_ are the ones that get to send pull 
requests directly to the Benevolent Dictator for Life?


b.g.

-- 
Bill Gatliff
bgat@billgatliff.com


      reply	other threads:[~2009-08-25 19:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-24 13:40 ARM subarch submissions for next merge window Kevin Hilman
2009-08-24 19:52 ` Linus Torvalds
2009-08-25 19:48   ` Bill Gatliff [this message]

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=4A94402A.1090003@billgatliff.com \
    --to=bgat@billgatliff.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=khilman@deeprootsystems.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-arm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nico@cam.org \
    --cc=rmk@arm.linux.org.uk \
    --cc=tony@atomide.com \
    --cc=torvalds@linux-foundation.org \
    /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