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,
David Herrmann <dh.herrmann@gmail.com>,
Peter Jones <pjones@redhat.com>,
stable@vger.kernel.org, Tomi Valkeinen <tomi.valkeinen@ti.com>,
Wang YanQing <udknight@gmail.com>
Subject: [GIT PULL v2] EFI urgent fix
Date: Thu, 5 May 2016 14:14:20 +0100 [thread overview]
Message-ID: <1462454061-21561-1-git-send-email-matt@codeblueprint.co.uk> (raw)
Folks, please pull the following with from Wang which includes a
rewritten changelog as compared with the previous pull request.
The following changes since commit 04974df8049fc4240d22759a91e035082ccd18b4:
Linux 4.6-rc6 (2016-05-01 15:52:31 -0700)
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 8491332837eed61cd5d47613b33cba90b809f36a:
x86/sysfb_efi: Fix valid BAR address range check (2016-05-05 13:14:04 +0100)
----------------------------------------------------------------
* Fix sysfb_efi to detect BARs starting at 0x0, which otherwise makes
video=efifb not work on some the ThinkPad E550 - Wang YanQing
----------------------------------------------------------------
Wang YanQing (1):
x86/sysfb_efi: Fix valid BAR address range check
arch/x86/kernel/sysfb_efi.c | 14 ++++++++++++--
1 file changed, 12 insertions(+), 2 deletions(-)
next reply other threads:[~2016-05-05 13:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-05 13:14 Matt Fleming [this message]
2016-05-05 13:14 ` [PATCH] x86/sysfb_efi: Fix valid BAR address range check 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=1462454061-21561-1-git-send-email-matt@codeblueprint.co.uk \
--to=matt@codeblueprint.co.uk \
--cc=ard.biesheuvel@linaro.org \
--cc=dh.herrmann@gmail.com \
--cc=hpa@zytor.com \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=pjones@redhat.com \
--cc=stable@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=tomi.valkeinen@ti.com \
--cc=udknight@gmail.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).