From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Ian Molton <spyro@f2s.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] arm26 arch and include updates
Date: Sun, 19 Dec 2004 13:15:12 +1100 [thread overview]
Message-ID: <41C4E430.4090807@yahoo.com.au> (raw)
In-Reply-To: <41C493A2.30703@f2s.com>
Ian Molton wrote:
> Any takers? I know I dont get a massive amount of time to work on this
> but it would be nice to keep what I have in sync with the tree when
> others make global changes.
Not that I'm qualified to comment about the architecture at all.
But it sounds like it is an improvement over what is currently in
there. Seeing as you're listed as ARM26 maintainer, and the patch
being completely contained to arm26, I'm sure you could get it
included quite easily ;)
The patch isn't _that_ big, but if you broke it up into a series, and
posted them (inline) to lkml, I'm sure Andrew Morton would queue them
up for after 2.6.10 for you (make sure he sees them).
Or alternatively, if it is accompanied by a quite detailed changelog,
often these sort of updates can be taken in as a single patch.
Good luck!
Nick
prev parent reply other threads:[~2004-12-19 2:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-17 3:42 [PATCH] arm26 arch and include updates Ian Molton
2004-12-18 20:31 ` Ian Molton
2004-12-19 2:15 ` Nick Piggin [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=41C4E430.4090807@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=spyro@f2s.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