From: Matt Fleming <matt@codeblueprint.co.uk>
To: Ingo Molnar <mingo@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
"H . Peter Anvin" <hpa@zytor.com>
Cc: Matt Fleming <matt@codeblueprint.co.uk>,
Ard Biesheuvel <ard.biesheuvel@linaro.org>,
linux-kernel@vger.kernel.org, linux-efi@vger.kernel.org,
Alex Thorlton <athorlton@sgi.com>, Borislav Petkov <bp@suse.de>,
Dimitri Sivanich <sivanich@sgi.com>,
Ingo Molnar <mingo@redhat.com>, Mike Travis <travis@sgi.com>,
Russ Anderson <rja@sgi.com>,
stable@vger.kernel.org, x86@kernel.org
Subject: [GIT PULL] EFI urgent fix
Date: Fri, 13 May 2016 21:34:41 +0100 [thread overview]
Message-ID: <1463171682-13881-1-git-send-email-matt@codeblueprint.co.uk> (raw)
The following changes since commit c10fcb14c7afd6688c7b197a814358fecf244222:
x86/sysfb_efi: Fix valid BAR address range check (2016-05-05 16:01:00 +0200)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/mfleming/efi.git tags/efi-urgent
for you to fetch changes up to 6f4c184576aeb5594b8d21f9e7206b7b62e3d96e:
x86/efi: Fix 7th argument to efi_call (2016-05-13 21:12:13 +0100)
----------------------------------------------------------------
* Fix passing of 7 parameters or more to efi_call. This issue is only
triggered on SGI/UV systems - Alex Thorlton
----------------------------------------------------------------
Alex Thorlton (1):
x86/efi: Fix 7th argument to efi_call
arch/x86/platform/efi/efi_stub_64.S | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
next reply other threads:[~2016-05-13 20:34 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-13 20:34 Matt Fleming [this message]
2016-05-13 20:34 ` [PATCH] x86/efi: Fix 7th argument to efi_call Matt Fleming
2016-05-16 10:40 ` [tip:efi/urgent] x86/efi: Fix 7th argument to efi_call() tip-bot for Alex Thorlton
-- strict thread matches above, loose matches on Subject: below --
2017-04-12 15:27 [GIT PULL] EFI urgent fix Matt Fleming
2017-01-27 22:06 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-06-11 12:47 Matt Fleming
2015-06-11 14:43 ` Ingo Molnar
2015-06-12 15:00 ` Matt Fleming
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=1463171682-13881-1-git-send-email-matt@codeblueprint.co.uk \
--to=matt@codeblueprint.co.uk \
--cc=ard.biesheuvel@linaro.org \
--cc=athorlton@sgi.com \
--cc=bp@suse.de \
--cc=hpa@zytor.com \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=mingo@redhat.com \
--cc=rja@sgi.com \
--cc=sivanich@sgi.com \
--cc=stable@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=travis@sgi.com \
--cc=x86@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;
as well as URLs for NNTP newsgroup(s).