From: Ingo Molnar <mingo@kernel.org>
To: Matt Fleming <matt@codeblueprint.co.uk>
Cc: "H. Peter Anvin" <hpa@zytor.com>,
Thomas Gleixner <tglx@linutronix.de>,
linux-efi@vger.kernel.org, linux-kernel@vger.kernel.org,
Peter Jones <pjones@redhat.com>,
Guenter Roeck <linux@roeck-us.net>,
"Luck, Tony" <tony.luck@intel.com>
Subject: Re: [GIT PULL] EFI urgent fix
Date: Thu, 11 Jun 2015 16:43:58 +0200 [thread overview]
Message-ID: <20150611144358.GA12476@gmail.com> (raw)
In-Reply-To: <20150611124758.GA19243@codeblueprint.co.uk>
* Matt Fleming <matt@codeblueprint.co.uk> wrote:
> Folks, please pull the following build fix from Peter Jones. Guenter
> reported that the ESRT driver doesn't build properly on ia64. The
> problem was discovered in linux-next.
>
> The following changes since commit c208358c2cc832eeb5b341a465eee30be19cd5a0:
>
> efi: Add 'systab' information to Documentation/ABI (2015-05-27 15:40:20 +0100)
>
> 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 3846c15820a1841225d0245afda4875af23dfbbe:
>
> efi: Work around ia64 build problem with ESRT driver (2015-06-08 10:51:31 +0100)
>
> ----------------------------------------------------------------
> * Fix ESRT build breakage on ia64 reported by Guenter Roeck - Peter Jones
>
> ----------------------------------------------------------------
> Peter Jones (1):
> efi: Work around ia64 build problem with ESRT driver
>
> drivers/firmware/efi/Kconfig | 5 +++++
> drivers/firmware/efi/Makefile | 3 ++-
> include/linux/efi.h | 4 ++++
> 3 files changed, 11 insertions(+), 1 deletion(-)
So I pulled this into tip:x86/efi, not into tip:x86/urgent, because the commit
that broke the ia64 build is not upstream yet.
Thanks,
Ingo
next prev parent reply other threads:[~2015-06-11 14:44 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-11 12:47 [GIT PULL] EFI urgent fix Matt Fleming
2015-06-11 14:43 ` Ingo Molnar [this message]
2015-06-12 15:00 ` Matt Fleming
-- strict thread matches above, loose matches on Subject: below --
2017-04-12 15:27 Matt Fleming
2017-01-27 22:06 Matt Fleming
2016-05-13 20:34 Matt Fleming
2016-04-25 11:26 Matt Fleming
2016-04-25 15:29 ` Ingo Molnar
2016-04-01 19:03 Matt Fleming
2016-04-02 7:32 ` Ingo Molnar
2015-11-04 10:47 Matt Fleming
2015-11-04 10:50 ` Thomas Gleixner
2015-10-16 10:01 Matt Fleming
2015-10-16 10:04 ` Ingo Molnar
2015-10-12 14:13 Matt Fleming
2015-07-15 14:31 Matt Fleming
2015-07-21 7:53 ` Ingo Molnar
2015-03-27 19:18 Matt Fleming
2014-09-19 10:33 Matt Fleming
2014-09-19 10:50 ` Ingo Molnar
2014-08-06 9:46 Matt Fleming
2014-07-07 6:43 Matt Fleming
2014-06-20 9:00 Matt Fleming
2014-06-20 9:28 ` Catalin Marinas
2014-06-20 13:39 ` Leif Lindholm
2014-06-20 13:49 ` Matt Fleming
2014-06-20 14:19 ` Leif Lindholm
2014-06-25 20:42 ` Matt Fleming
2014-05-03 5:51 Matt Fleming
2014-05-04 18:21 ` Ingo Molnar
2014-03-04 23:47 Matt Fleming
2013-09-19 12:41 Matt Fleming
2013-09-20 7:53 ` Ingo Molnar
2013-06-21 9:56 Matt Fleming
2013-04-26 16:30 Matt Fleming
2013-04-26 16:40 ` Linus Torvalds
2013-04-26 16:48 ` 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=20150611144358.GA12476@gmail.com \
--to=mingo@kernel.org \
--cc=hpa@zytor.com \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=matt@codeblueprint.co.uk \
--cc=pjones@redhat.com \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.com \
/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;
as well as URLs for NNTP newsgroup(s).