From: Andrew Morton <akpm@linux-foundation.org>
To: Marcelo Roberto Jimenez <mroberto@cetuc.puc-rio.br>
Cc: linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-pcmcia@lists.infradead.org, linux@arm.linux.org.uk,
mad_soft@inbox.ru, rpjday@crashcourse.ca,
jaswinderrajput@gmail.com, kristoffer.ericson@gmail.com,
Dominik Brodowski <linux@dominikbrodowski.net>,
Russell King <rmk+kernel@arm.linux.org.uk>,
Wolfram Sang <w.sang@pengutronix.de>,
Alessandro Zummo <a.zummo@towertech.it>,
rtc-linux@googlegroups.com
Subject: Re: Pull request for nanoengine
Date: Wed, 2 Jun 2010 16:38:44 -0700 [thread overview]
Message-ID: <20100602163844.509e9953.akpm@linux-foundation.org> (raw)
In-Reply-To: <AANLkTilh4NtHS5p3tWbMtIU9MBBC-Md13Aw9_RdL3Ogp@mail.gmail.com>
On Wed, 2 Jun 2010 20:19:01 -0300
Marcelo Roberto Jimenez <mroberto@cetuc.puc-rio.br> wrote:
> The following is a compilation of all the patches I have done for the
> nanoengine. Some of these are also valid for SA11xx based machines
> like, e.g, sharp Zaurus.
Which other kernel developer were you hoping would merge this tree?
> arch/arm/configs/nanoengine_defconfig | 1396 ++++++++++++++++++++++++
> arch/arm/mach-sa1100/Kconfig | 8 +
> arch/arm/mach-sa1100/Makefile | 2 +
> arch/arm/mach-sa1100/cpu-sa1100.c | 56 +-
> arch/arm/mach-sa1100/cpu-sa1110.c | 51 +-
> arch/arm/mach-sa1100/include/mach/nanoengine.h | 30 +
> arch/arm/mach-sa1100/nanoengine.c | 115 ++
> drivers/pcmcia/Makefile | 3 +-
> drivers/pcmcia/sa1100_generic.c | 3 +
> drivers/pcmcia/sa1100_generic.h | 1 +
> drivers/pcmcia/sa1100_nanoengine.c | 219 ++++
> drivers/pcmcia/soc_common.c | 129 ++-
> drivers/rtc/rtc-sa1100.c | 153 ++-
I can only think it must have been Russell.
I've rather lost track of what's happening with ARM subtrees. I
_think_ it's now the case the relevant maintainers are putting their
trees into linux-next directly and are asking Linus to pull them
directly. But maybe that's a misconception.
Can someone please explain the current state of play?
Thanks.
next prev parent reply other threads:[~2010-06-02 23:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-02 23:19 Marcelo Roberto Jimenez
2010-06-02 23:38 ` Andrew Morton [this message]
2010-06-03 1:22 ` Randy Dunlap
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=20100602163844.509e9953.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=a.zummo@towertech.it \
--cc=jaswinderrajput@gmail.com \
--cc=kristoffer.ericson@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pcmcia@lists.infradead.org \
--cc=linux@arm.linux.org.uk \
--cc=linux@dominikbrodowski.net \
--cc=mad_soft@inbox.ru \
--cc=mroberto@cetuc.puc-rio.br \
--cc=rmk+kernel@arm.linux.org.uk \
--cc=rpjday@crashcourse.ca \
--cc=rtc-linux@googlegroups.com \
--cc=w.sang@pengutronix.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
Powered by JetHome