From: catalin.marinas@arm.com (Catalin Marinas)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL v3] Linux support for ARM LPAE
Date: Thu, 8 Dec 2011 18:08:28 +0000 [thread overview]
Message-ID: <20111208180828.GE27757@arm.com> (raw)
In-Reply-To: <20111208180536.GK14542@n2100.arm.linux.org.uk>
On Thu, Dec 08, 2011 at 06:05:36PM +0000, Russell King - ARM Linux wrote:
> On Thu, Dec 08, 2011 at 11:03:49AM +0000, Catalin Marinas wrote:
> > The series is rebased against Will's idmap series as merged in your
> > devel-stable tree (I couldn't fetch devel-stable this morning). Please
> > note that the branch was changed to 'for-rmk' (previously 'for-next').
> > The nopud fixup was already reordered so that it comes before your
> > patch.
>
> Thank you.
>
> Now pulled and merged - with the expected conflict in ioremap.c between
> your commits and 576d2f25 resolved.
>
> I'll push it out shortly, so it should land in linux-next this evening.
Great! Thanks.
--
Catalin
prev parent reply other threads:[~2011-12-08 18:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-08 11:03 [GIT PULL v3] Linux support for ARM LPAE Catalin Marinas
2011-12-08 18:05 ` Russell King - ARM Linux
2011-12-08 18:08 ` Catalin Marinas [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=20111208180828.GE27757@arm.com \
--to=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.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).