From: khilman@deeprootsystems.com (Kevin Hilman)
To: linux-arm-kernel@lists.infradead.org
Subject: ARM subarch submissions for next merge window
Date: Mon, 24 Aug 2009 16:40:10 +0300 [thread overview]
Message-ID: <877hwtnxdx.fsf@deeprootsystems.com> (raw)
Linus,
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?
Kevin
maintainer: arch/arm/mach-davinci/*
developer: arch/arm/mach-omap2/*
[1] http://marc.info/?l=linux-arm-kernel&m=124472557106678&w=2
[2] http://marc.info/?l=linux-kernel&m=124472614607233&w=2
next reply other threads:[~2009-08-24 13:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-24 13:40 Kevin Hilman [this message]
2009-08-24 19:52 ` ARM subarch submissions for next merge window Linus Torvalds
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=877hwtnxdx.fsf@deeprootsystems.com \
--to=khilman@deeprootsystems.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).