From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Russell King <rmk+lkml@arm.linux.org.uk>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Randy Dunlap <randy.dunlap@oracle.com>,
Pavel Machek <pavel@suse.cz>, "Rafael J. Wysocki" <rjw@sisk.pl>,
linux-stable@vger.kernel.org, Stanislav Brabec <utx@penguin.cz>,
kernel list <linux-kernel@vger.kernel.org>,
rpurdie@rpsys.net, lenz@cs.wisc.edu, Dirk@opfer-online.de,
arminlitzel@web.de, pavel.urban@ct.cz,
metan@atrey.karlin.mff.cuni.cz, thommycheck@gmail.com,
milan@ucw.cz
Subject: Re: [Patch 2.6.27] fix booting on Sharp Zaurus c3000
Date: Tue, 28 Oct 2008 09:24:49 +0000 [thread overview]
Message-ID: <20081028092449.3123fe39@lxorguk.ukuu.org.uk> (raw)
In-Reply-To: <20081028084407.GA7913@flint.arm.linux.org.uk>
> Since it's a trivial documentation matter, don't we have someone
> handling such patches? Is Rusty still the Trivial Patch Monkey?
Randy is the documentation maintainer (see MAINTAINERS)
Sounds like it should just go in directly not through the ARM tree
next prev parent reply other threads:[~2008-10-28 9:26 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-09 9:19 2.6.27-rc8 regression on arm: kernel will no longer boot on Sharp Zaurus c-3000 Pavel Machek
2008-10-09 12:00 ` Stanislav Brabec
2008-10-09 14:23 ` Russell King
2008-10-15 10:17 ` Pavel Machek
2008-10-15 11:39 ` Russell King
2008-10-24 22:01 ` Rafael J. Wysocki
2008-10-26 18:41 ` [Patch 2.6.27] fix booting on Sharp Zaurus c3000 Pavel Machek
2008-10-27 16:25 ` Randy Dunlap
2008-10-28 6:42 ` Andrew Morton
2008-10-28 8:44 ` Russell King
2008-10-28 9:24 ` Alan Cox [this message]
2008-10-28 17:56 ` Randy Dunlap
2008-11-07 18:43 ` [PATCH] arm: fix kernel-doc syntax Randy Dunlap
2008-10-28 18:24 ` [Patch 2.6.27] fix booting on Sharp Zaurus c3000 Pavel Machek
2008-10-28 20:05 ` Randy Dunlap
2008-10-09 16:28 ` 2.6.27-rc8 regression on arm: kernel will no longer boot on Sharp Zaurus c-3000 Russell King
2008-10-12 8:53 ` Pavel Machek
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=20081028092449.3123fe39@lxorguk.ukuu.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=Dirk@opfer-online.de \
--cc=akpm@linux-foundation.org \
--cc=arminlitzel@web.de \
--cc=lenz@cs.wisc.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stable@vger.kernel.org \
--cc=metan@atrey.karlin.mff.cuni.cz \
--cc=milan@ucw.cz \
--cc=pavel.urban@ct.cz \
--cc=pavel@suse.cz \
--cc=randy.dunlap@oracle.com \
--cc=rjw@sisk.pl \
--cc=rmk+lkml@arm.linux.org.uk \
--cc=rpurdie@rpsys.net \
--cc=thommycheck@gmail.com \
--cc=utx@penguin.cz \
/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
all inboxes | Powered by JetHome®