From: Tony Luck <tony.luck@gmail.com>
To: Leif Lindholm <leif.lindholm@linaro.org>
Cc: "linux-efi@vger.kernel.org" <linux-efi@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"linux-ia64@vger.kernel.org" <linux-ia64@vger.kernel.org>,
Matt Fleming <matt.fleming@intel.com>,
"H. Peter Anvin" <hpa@zytor.com>,
Thomas Gleixner <tglx@linutronix.de>,
patches@linaro.org
Subject: Re: [PATCH 1/4] efi: provide a generic efi_config_init()
Date: Tue, 30 Jul 2013 18:14:51 +0000 [thread overview]
Message-ID: <CA+8MBbLbsrH=gNJ4oc5VzphY6xFMthWoq5R905Rzaow2SmA9uw@mail.gmail.com> (raw)
In-Reply-To: <20130730180230.GJ18151@rocoto.smurfnet.nu>
On Tue, Jul 30, 2013 at 11:02 AM, Leif Lindholm
<leif.lindholm@linaro.org> wrote:
> So I guess the clean way to deal with that would be to make the
> memremap definition a separate patch?
Or just pull:
+#define early_memremap(phys_addr, size) early_ioremap(phys_addr, size)
out of part 3 and put it into part1 (along with some of the commit commentary).
-Tony
next prev parent reply other threads:[~2013-07-30 18:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-30 16:47 [PATCH 0/4] Make commonly useful UEFI functions common Leif Lindholm
2013-07-30 16:47 ` [PATCH 1/4] efi: provide a generic efi_config_init() Leif Lindholm
2013-07-30 17:53 ` Tony Luck
2013-07-30 18:02 ` Leif Lindholm
2013-07-30 18:14 ` Tony Luck [this message]
2013-07-30 16:47 ` [PATCH 2/4] efi: x86: use common code for (U)EFI configuration scanning Leif Lindholm
2013-07-30 16:47 ` [PATCH 3/4] efi: ia64: " Leif Lindholm
2013-07-30 16:47 ` [PATCH 4/4] efi: x86: make efi_lookup_mapped_addr() a common function Leif Lindholm
2013-07-31 8:58 ` Matt Fleming
2013-08-01 10:11 ` Leif Lindholm
2013-07-30 19:57 ` [PATCH 0/4] Make commonly useful UEFI functions common Tony Luck
2013-08-01 20:26 ` H. Peter Anvin
2013-08-01 20:45 ` Fleming, Matt
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='CA+8MBbLbsrH=gNJ4oc5VzphY6xFMthWoq5R905Rzaow2SmA9uw@mail.gmail.com' \
--to=tony.luck@gmail.com \
--cc=hpa@zytor.com \
--cc=leif.lindholm@linaro.org \
--cc=linux-efi@vger.kernel.org \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matt.fleming@intel.com \
--cc=patches@linaro.org \
--cc=tglx@linutronix.de \
/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).