From: "David S. Miller" <davem@davemloft.net>
To: Russell King <rmk@arm.linux.org.uk>
Cc: benh@kernel.crashing.org, linux-arch@vger.kernel.org
Subject: Re: Changing update_mmu_cache()
Date: Tue, 22 Feb 2005 10:08:58 -0800 [thread overview]
Message-ID: <20050222100858.27d05a86.davem@davemloft.net> (raw)
In-Reply-To: <20050222090741.B16786@flint.arm.linux.org.uk>
On Tue, 22 Feb 2005 09:07:41 +0000
Russell King <rmk@arm.linux.org.uk> wrote:
> On Tue, Feb 22, 2005 at 03:53:17PM +1100, Benjamin Herrenschmidt wrote:
> > Is that ok with everybody ?
>
> On the grounds that I can't get my MM changes past Linus which I need
> for newer ARM CPUs, so I don't see why this change which adds extra code
> (which is the complaint against my changes) should be considered.
It doesn't add extra code:
1) the pte gets deref'd currently anyways
2) platforms not using the pte pointer arg will simply get that
argument optimized away
Russell, send me what you're having trouble merging under seperate
cover and I'll give you a hand, from one old man to another :-)
next prev parent reply other threads:[~2005-02-22 18:08 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 [this message]
2005-02-25 20:15 ` Russell King
2005-02-25 21:43 ` Andrew Morton
2005-02-25 21:46 ` William Lee Irwin III
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=20050222100858.27d05a86.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=benh@kernel.crashing.org \
--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