From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Russell King <rmk@arm.linux.org.uk>
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:49:40 +0100 [thread overview]
Message-ID: <10f740e81002281049g3f56ec78v28dfff1a9ab85102@mail.gmail.com> (raw)
In-Reply-To: <20100228180419.GA3480@rmk-PC.arm.linux.org.uk>
On Sun, Feb 28, 2010 at 19:04, Russell King <rmk@arm.linux.org.uk> wrote:
> Linus, Andrew,
>
> Please incorporate the latest ARM (for-linus branch) changes, which can be found at:
>
> master.kernel.org:/home/rmk/linux-2.6-arm.git for-linus
Any specific reason this tree is not stored in
/pub/scm/linux/kernel/git/rmk/, so
mere mortals can access it?
> 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?
Thanks!
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next prev parent reply other threads:[~2010-02-28 18:49 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 [this message]
2010-02-28 19:02 ` Russell King
2010-02-28 19:41 ` Geert Uytterhoeven
2010-02-28 19:45 ` Russell King
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=10f740e81002281049g3f56ec78v28dfff1a9ab85102@mail.gmail.com \
--to=geert@linux-m68k.org \
--cc=akpm@linux-foundation.org \
--cc=linux-arch@vger.kernel.org \
--cc=rmk@arm.linux.org.uk \
--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).