From: Catalin Marinas <catalin.marinas@arm.com>
To: Matt Fleming <matt@console-pimps.org>
Cc: "H. Peter Anvin" <hpa@zytor.com>, Ingo Molnar <mingo@kernel.org>,
Leif Lindholm <leif.lindholm@linaro.org>,
"linux-efi@vger.kernel.org" <linux-efi@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] EFI changes for arm64
Date: Tue, 20 May 2014 17:28:14 +0100 [thread overview]
Message-ID: <20140520162814.GB28293@arm.com> (raw)
In-Reply-To: <20140519105042.GE4798@console-pimps.org>
On Mon, May 19, 2014 at 11:50:42AM +0100, Matt Fleming wrote:
> On Wed, 30 Apr, at 09:03:32PM, Matt Fleming wrote:
> > I pulled the arm64 EFI changes into the following topic branch. Catalin
> > was happy for this to go through tip, which definitely makes things
> > easier for the next merge window because of the dependency these patches
> > have on tip/x86/efi.
> >
> > The following changes since commit e33655a386ed3b26ad36fb97a47ebb1c2ca1e928:
> >
> > efivars: Add compatibility code for compat tasks (2014-04-17 13:53:53 +0100)
> >
> > are available in the git repository at:
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/mfleming/efi.git arm64-efi
> >
> > for you to fetch changes up to 345c736edd07b657a8c48190baed2719b85d0938:
> >
> > efi/arm64: ignore dtb= when UEFI SecureBoot is enabled (2014-04-30 19:57:06 +0100)
>
> Ping?
Alternatively, I can merge the arm64-efi tree and wait for tip x86/efi
to go in before sending my pull request. Peter, Ingo, do you have any
preference?
Either way, I'd like to see this branch in -next to make sure there are
no (significant) conflicts before the merging window.
Thanks.
--
Catalin
next prev parent reply other threads:[~2014-05-20 16:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-30 20:03 Matt Fleming
2014-05-19 10:50 ` Matt Fleming
2014-05-20 16:28 ` Catalin Marinas [this message]
2014-05-23 22:23 Matt Fleming
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=20140520162814.GB28293@arm.com \
--to=catalin.marinas@arm.com \
--cc=hpa@zytor.com \
--cc=leif.lindholm@linaro.org \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matt@console-pimps.org \
--cc=mingo@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
Powered by JetHome