From: William Lee Irwin III <wli@holomorphy.com>
To: Andrew Morton <akpm@osdl.org>
Cc: Russell King <rmk@arm.linux.org.uk>,
davem@davemloft.net, linux-arch@vger.kernel.org
Subject: Re: Changing update_mmu_cache()
Date: Fri, 25 Feb 2005 13:46:37 -0800 [thread overview]
Message-ID: <20050225214637.GQ15648@holomorphy.com> (raw)
In-Reply-To: <20050225134322.43274a9a.akpm@osdl.org>
Russell King <rmk@arm.linux.org.uk> wrote:
>> The problem I now face is that we're almost at 2.6.11, and its been
>> almost three months, so I think it's safe to assume that Linus will
>> have forgotten everything about this, and will probably hate the
>> patch next time around. But maybe I'm underestimating Linus.
On Fri, Feb 25, 2005 at 01:43:22PM -0800, Andrew Morton wrote:
> What does it do? Just adds a pfn arg to flush_cache_page()? We do that
> sort of thing quite a lot, and I can help.
> A typical approach would be to send me a patch for the core kernel, a patch
> for x86 and a patch for arm. Any additional best-effort per-architecture
> patches would be appreciated as well, of course.
> I test of four architectures and compile on seven. arch maintainers will
> develop, test and submit their bits and when all the ducks are lined up
> I'll send it all off to Linus.
> The main problem is that people are hacking on mm/* all the damn time, so
> I have to live with massive reject storms during the changeover period.
> But that's my problem, not yours ;)
I do many-architecture testing also, and I'd be willing to help with
sweeps.
-- wli
next prev parent reply other threads:[~2005-02-25 21:46 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-22 4:53 Changing update_mmu_cache() Benjamin Herrenschmidt
2005-02-22 5:43 ` David S. Miller
2005-02-22 9:07 ` Russell King
2005-02-22 18:08 ` David S. Miller
2005-02-25 20:15 ` Russell King
2005-02-25 21:43 ` Andrew Morton
2005-02-25 21:46 ` William Lee Irwin III [this message]
2005-02-25 22:48 ` Russell King
2005-02-25 22:59 ` William Lee Irwin III
2005-02-25 23:07 ` Andrew Morton
2005-02-26 1:09 ` David S. Miller
2005-02-27 18:55 ` Paul Mundt
2005-02-28 4:12 ` David S. Miller
2005-02-28 9:18 ` Paul Mundt
2005-03-06 5:15 ` David S. Miller
2005-02-27 19:27 ` Russell King
2005-02-26 1:10 ` Benjamin Herrenschmidt
2005-02-22 20:51 ` Benjamin Herrenschmidt
2005-02-23 5:35 ` Changing update_mmu_cache() or set_pte() ? Benjamin Herrenschmidt
2005-02-23 5:47 ` Benjamin Herrenschmidt
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=20050225214637.GQ15648@holomorphy.com \
--to=wli@holomorphy.com \
--cc=akpm@osdl.org \
--cc=davem@davemloft.net \
--cc=linux-arch@vger.kernel.org \
--cc=rmk@arm.linux.org.uk \
/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