All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matt Fleming <matt@codeblueprint.co.uk>
To: "H. Peter Anvin" <hpa@zytor.com>, Ingo Molnar <mingo@kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>
Cc: linux-efi@vger.kernel.org, linux-kernel@vger.kernel.org,
	Ricardo Neri <ricardo.neri-calderon@linux.intel.com>
Subject: Re: [GIT PULL] EFI changes for v3.20
Date: Mon, 26 Jan 2015 22:32:20 +0000	[thread overview]
Message-ID: <20150126223220.GF3320@codeblueprint.co.uk> (raw)
In-Reply-To: <20150121140250.GE12079@codeblueprint.co.uk>

On Wed, 21 Jan, at 02:02:50PM, Matt Fleming wrote:
> Folks, please consider pulling the following changes for v3.20. There's
> nothing super scary, mainly cleanups, and a merge from Ricardo who
> kindly picked up some patches from the linux-efi mailing list while I
> was out on annual leave in December.
> 
> Perhaps the biggest risk is the get_memory_map() change from Ard, which
> changes the way that both the arm64 and x86 EFI boot stub build the
> early memory map. It would be good to have it bake in linux-next for a
> while.
> 
> One other thing to note is that I've picked up an rtc-efi patch from Ard
> because the rtc maintainer hasn't been responsive for a while now.
> 
> The following changes since commit 8266e31ed0fedb7ee16ebc86e80468f7cc1bbb4e:
> 
>   x86, ptdump: Add section for EFI runtime services (2014-11-11 22:28:57 +0000)
> 
> are available in the git repository at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/mfleming/efi.git tags/efi-next
> 
> for you to fetch changes up to 11629305043c513454c4ccb4fc384a1bfe610647:
> 
>   efi: Don't look for chosen@0 node on DT platforms (2015-01-20 22:41:56 +0000)

Ping?

-- 
Matt Fleming, Intel Open Source Technology Center

WARNING: multiple messages have this Message-ID (diff)
From: Matt Fleming <matt-mF/unelCI9GS6iBeEJttW/XRex20P6io@public.gmane.org>
To: "H. Peter Anvin" <hpa-YMNOUZJC4hwAvxtiuMwx3w@public.gmane.org>,
	Ingo Molnar <mingo-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
	Thomas Gleixner <tglx-hfZtesqFncYOwBW4kG4KsQ@public.gmane.org>
Cc: linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	Ricardo Neri
	<ricardo.neri-calderon-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
Subject: Re: [GIT PULL] EFI changes for v3.20
Date: Mon, 26 Jan 2015 22:32:20 +0000	[thread overview]
Message-ID: <20150126223220.GF3320@codeblueprint.co.uk> (raw)
In-Reply-To: <20150121140250.GE12079-mF/unelCI9GS6iBeEJttW/XRex20P6io@public.gmane.org>

On Wed, 21 Jan, at 02:02:50PM, Matt Fleming wrote:
> Folks, please consider pulling the following changes for v3.20. There's
> nothing super scary, mainly cleanups, and a merge from Ricardo who
> kindly picked up some patches from the linux-efi mailing list while I
> was out on annual leave in December.
> 
> Perhaps the biggest risk is the get_memory_map() change from Ard, which
> changes the way that both the arm64 and x86 EFI boot stub build the
> early memory map. It would be good to have it bake in linux-next for a
> while.
> 
> One other thing to note is that I've picked up an rtc-efi patch from Ard
> because the rtc maintainer hasn't been responsive for a while now.
> 
> The following changes since commit 8266e31ed0fedb7ee16ebc86e80468f7cc1bbb4e:
> 
>   x86, ptdump: Add section for EFI runtime services (2014-11-11 22:28:57 +0000)
> 
> are available in the git repository at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/mfleming/efi.git tags/efi-next
> 
> for you to fetch changes up to 11629305043c513454c4ccb4fc384a1bfe610647:
> 
>   efi: Don't look for chosen@0 node on DT platforms (2015-01-20 22:41:56 +0000)

Ping?

-- 
Matt Fleming, Intel Open Source Technology Center

  reply	other threads:[~2015-01-26 22:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-21 14:02 [GIT PULL] EFI changes for v3.20 Matt Fleming
2015-01-21 14:02 ` Matt Fleming
2015-01-26 22:32 ` Matt Fleming [this message]
2015-01-26 22:32   ` Matt Fleming
2015-01-28 14:51   ` Ingo Molnar
2015-01-28 14:51     ` Ingo Molnar
2015-01-29 18:21   ` Ingo Molnar

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=20150126223220.GF3320@codeblueprint.co.uk \
    --to=matt@codeblueprint.co.uk \
    --cc=hpa@zytor.com \
    --cc=linux-efi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=ricardo.neri-calderon@linux.intel.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.