From: Matt Fleming <matt@console-pimps.org>
To: Ingo Molnar <mingo@kernel.org>
Cc: "H. Peter Anvin" <hpa@zytor.com>,
Thomas Gleixner <tglx@linutronix.de>,
linux-efi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] EFI runtime mapping work for v3.14
Date: Mon, 11 Nov 2013 11:38:09 +0000 [thread overview]
Message-ID: <20131111113809.GF22636@console-pimps.org> (raw)
In-Reply-To: <20131111111754.GB15810@gmail.com>
On Mon, 11 Nov, at 12:17:54PM, Ingo Molnar wrote:
>
> * Matt Fleming <matt@console-pimps.org> wrote:
>
> > Folks, could you queue up the following for the v3.14 merge window? It
> > would be good to get these patches into linux-next for a full release
> > cycle of testing. They pass all of my tests.
> >
> > The following changes since commit 72548e836b0c4abbb652e791dee9c91203a9a4c6:
> >
> > x86/efi: Add EFI framebuffer earlyprintk support (2013-10-28 18:09:58 +0000)
> >
> > are available in the git repository at:
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/mfleming/efi.git tags/efi-next
>
> Mind resending this in about a week or so? The merge window has just
> started and we don't want to potentially destabilize -next with v3.14
> problems.
Sure, no problem at all.
--
Matt Fleming, Intel Open Source Technology Center
next prev parent reply other threads:[~2013-11-11 11:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-08 10:57 [GIT PULL] EFI runtime mapping work for v3.14 Matt Fleming
2013-11-11 11:17 ` Ingo Molnar
2013-11-11 11:38 ` Matt Fleming [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-11-25 16:28 Matt Fleming
2013-11-26 11:26 ` Ingo Molnar
2013-11-26 11:56 ` Borislav Petkov
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=20131111113809.GF22636@console-pimps.org \
--to=matt@console-pimps.org \
--cc=hpa@zytor.com \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.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