From: Matt Fleming <matt-HNK1S37rvNbeXh+fF434Mdi2O/JbrIOy@public.gmane.org>
To: "H. Peter Anvin" <hpa-YMNOUZJC4hwAvxtiuMwx3w@public.gmane.org>
Cc: Ingo Molnar <mingo-X9Un+BFzKDI@public.gmane.org>,
Thomas Gleixner <tglx-hfZtesqFncYOwBW4kG4KsQ@public.gmane.org>,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-efi <linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [GIT PULL] EFI changes for v3.8
Date: Tue, 13 Nov 2012 22:20:45 +0000 [thread overview]
Message-ID: <1352845245.15747.113.camel@mfleming-mobl1.ger.corp.intel.com> (raw)
In-Reply-To: <50A2C572.30307-YMNOUZJC4hwAvxtiuMwx3w@public.gmane.org>
On Tue, 2012-11-13 at 14:10 -0800, H. Peter Anvin wrote:
> On 11/13/2012 02:00 PM, Matt Fleming wrote:
> > Hi guys,
> >
> > The following changes since commit 5189c2a7c7769ee9d037d76c1a7b8550ccf3481c:
> >
> > x86: efi: Turn off efi_enabled after setup on mixed fw/kernel (2012-10-25 19:09:40 +0100)
> >
> > are available in the git repository at:
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/mfleming/efi.git tags/efi-for-3.8
> >
> > for you to fetch changes up to fdafa1c8261d4fe2350e63e8dd315bfd58674455:
> >
>
> This is a lambda merge... are the commits in efi-for-3.7 already
> upstream? If so, there is no reason to include them in this pull request.
Yes, they are already upstream.
> For now I am going to put efi/next into -tip as core/efi. Please let me
> know if we should put the efi-for-3.7 into an urgent branch.
OK, thanks. No need to put efi-for-3.7 into an urgent branch.
--
Matt Fleming, Intel Open Source Technology Center
prev parent reply other threads:[~2012-11-13 22:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-13 22:00 [GIT PULL] EFI changes for v3.8 Matt Fleming
[not found] ` <1352844053.15747.111.camel-ZqTwcBeJ+wsBof6jY8KHXm7IUlhRatedral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2012-11-13 22:10 ` H. Peter Anvin
[not found] ` <50A2C572.30307-YMNOUZJC4hwAvxtiuMwx3w@public.gmane.org>
2012-11-13 22:20 ` 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=1352845245.15747.113.camel@mfleming-mobl1.ger.corp.intel.com \
--to=matt-hnk1s37rvnbexh+ff434mdi2o/jbrioy@public.gmane.org \
--cc=hpa-YMNOUZJC4hwAvxtiuMwx3w@public.gmane.org \
--cc=linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mingo-X9Un+BFzKDI@public.gmane.org \
--cc=tglx-hfZtesqFncYOwBW4kG4KsQ@public.gmane.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