linux-ia64.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matt Fleming <matt@console-pimps.org>
To: Leif Lindholm <leif.lindholm@linaro.org>
Cc: linux-efi@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-ia64@vger.kernel.org, matt.fleming@intel.com,
	tony.luck@gmail.com, grant.likely@secretlab.ca, x86@kernel.org
Subject: Re: [PATCH v4 0/3] Make commonly useful UEFI functions common
Date: Thu, 05 Sep 2013 13:21:06 +0000	[thread overview]
Message-ID: <20130905132106.GA7579@console-pimps.org> (raw)
In-Reply-To: <1378377295-32758-1-git-send-email-leif.lindholm@linaro.org>

On Thu, 05 Sep, at 11:34:52AM, Leif Lindholm wrote:
> This set breaks out some common code from x86/ia64 EFI support
> code and puts it into drivers/firmware/efi.
> 
> First it takes the definition of the global "efi" data structure
> and moves it into global efi.c. Then it implements a common version
> of efi_config_init().
> 
> Secondly it breaks the efi_lookup_mapped_addr() function out of x86
> and places it in global efi.c, for shared use with future ARM
> patches.
> 
> IA64 code compile tested only.
> 
> Leif Lindholm (3):
>   ia64: add early_memremap() alias for early_ioremap()
>   efi: x86: ia64: provide a generic efi_config_init()
>   efi: x86: make efi_lookup_mapped_addr() a common function
> 
>  arch/ia64/include/asm/io.h  |    1 +
>  arch/ia64/kernel/efi.c      |   54 ++++-------------
>  arch/x86/platform/efi/efi.c |  126 ++++----------------------------------
>  drivers/firmware/efi/efi.c  |  140 +++++++++++++++++++++++++++++++++++++++++++
>  include/linux/efi.h         |    8 +++
>  5 files changed, 170 insertions(+), 159 deletions(-)

Thanks Leif.

I've pulled this patch series into the 'arm/efi-stub' branch at,

  git://git.kernel.org/pub/scm/linux/kernel/git/mfleming/efi.git

as I know that Grant wanted these changes (and the subsequent patches)
in a clean branch.

Tip folks, how can we get the 'arm/efi-stub' branch into linux-next? My
plan was to merge 'arm/efi-stub' into my 'next' branch and ask you to
pull that into whichever branch you include in linux-next. Does that
work?

-- 
Matt Fleming, Intel Open Source Technology Center

      parent reply	other threads:[~2013-09-05 13:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-05 10:34 [PATCH v4 0/3] Make commonly useful UEFI functions common Leif Lindholm
2013-09-05 10:34 ` [PATCH v4 1/3] ia64: add early_memremap() alias for early_ioremap() Leif Lindholm
2013-09-05 10:34 ` [PATCH v4 2/3] efi: x86: ia64: provide a generic efi_config_init() Leif Lindholm
2013-09-05 10:34 ` [PATCH v4 3/3] efi: x86: make efi_lookup_mapped_addr() a common function Leif Lindholm
2013-09-05 13:21 ` Matt Fleming [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=20130905132106.GA7579@console-pimps.org \
    --to=matt@console-pimps.org \
    --cc=grant.likely@secretlab.ca \
    --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=tony.luck@gmail.com \
    --cc=x86@kernel.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).