public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Kevin Hilman <khilman@deeprootsystems.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Russell King <rmk@arm.linux.org.uk>,
	Tony Lindgren <tony@atomide.com>, Nicolas Pitre <nico@cam.org>,
	linux-kernel@vger.kernel.org, linux-arm@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: ARM subarch submissions for next merge window
Date: Mon, 24 Aug 2009 12:52:17 -0700 (PDT)	[thread overview]
Message-ID: <alpine.LFD.2.01.0908241249200.3158@localhost.localdomain> (raw)
In-Reply-To: <877hwtnxdx.fsf@deeprootsystems.com>



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.
> 
> Any changes that affect common ARM code will still be pushed via
> Russell, only our platform-specific code will be submitted directly.
> 
> Also our platform code is still posted and reviewed on
> linux-arm-kernel as well as being included in linux-next. Only the
> merge path will change slightly.
> 
> Any problems with this?

I don't have any issues with it, as long as the subarch trees are clean 
and clear.

Part of that is the normal "git cleanliness" issue in general (ie I don't 
want to see ugly back-merges of my random kernel-of-the-day or see that 
something was rebased just five minutes ago and clearly had no testing), 
but the other part is obviously that if there then ends up being 
complaints where people end up stepping on each others toes, I would want 
a top-level maintainer to step in.

But I guess that as long as it's clearly just platform-specific files, 
that won't be a problem.

		Linus

  reply	other threads:[~2009-08-24 19:53 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 [this message]
2009-08-25 19:48   ` Bill Gatliff

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=alpine.LFD.2.01.0908241249200.3158@localhost.localdomain \
    --to=torvalds@linux-foundation.org \
    --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 \
    /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