From: Russell King <rmk@arm.linux.org.uk>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-arch@vger.kernel.org
Subject: Re: [GIT PULL] ARM devel (pt 1) updates
Date: Sun, 28 Feb 2010 19:45:26 +0000 [thread overview]
Message-ID: <20100228194526.GD9546@flint.arm.linux.org.uk> (raw)
In-Reply-To: <10f740e81002281141u3a51f368u85830a1da20675dd@mail.gmail.com>
On Sun, Feb 28, 2010 at 08:41:22PM +0100, Geert Uytterhoeven wrote:
> On Sun, Feb 28, 2010 at 20:02, Russell King <rmk@arm.linux.org.uk> wrote:
> > On Sun, Feb 28, 2010 at 07:49:40PM +0100, Geert Uytterhoeven wrote:
> >> On Sun, Feb 28, 2010 at 19:04, Russell King <rmk@arm.linux.org.uk> wrote:
> >> > For linux-arch: this contains the patch
> >> > "MM: Pass a PTE pointer to update_mmu_cache() rather than the PTE itself"
> >> > which was previously sent to linux-arch for testing.
> >>
> >> Documentation/cachetlb.txt still lacks documentation for the `pte' parameter.
> >> Can you please fix that?
> >
> > Didn't I reply to your email about that? No response was forthcoming.
>
> Yes you did; you said "I'm open to suggestions for a suitable
> description for it.".
> Sorry, I forgot to reply that I find that a very uncommon attitude...
Well, what do you want there? "a pointer to the pte" - that's blatently
obvious from the fact that it's C declaration is "pte_t *".
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of:
prev parent reply other threads:[~2010-02-28 19:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-28 18:04 [GIT PULL] ARM devel (pt 1) updates Russell King
2010-02-28 18:49 ` Geert Uytterhoeven
2010-02-28 19:02 ` Russell King
2010-02-28 19:41 ` Geert Uytterhoeven
2010-02-28 19:45 ` Russell King [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=20100228194526.GD9546@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=akpm@linux-foundation.org \
--cc=geert@linux-m68k.org \
--cc=linux-arch@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/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;
as well as URLs for NNTP newsgroup(s).