mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Matt Fleming <matt@console-pimps.org>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>,
	linux-kernel@vger.kernel.org,
	linux-efi <linux-efi@vger.kernel.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@zytor.com>

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


      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 Matt Fleming
2012-11-13 22:10 ` H. Peter Anvin
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@console-pimps.org \
    --cc=hpa@zytor.com \
    --cc=linux-efi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --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

all inboxes | Powered by JetHome®