From: Ingo Molnar <mingo@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
Borislav Petkov <bp@alien8.de>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Andrew Morton <akpm@linux-foundation.org>
Subject: [GIT PULL] x86/boot changes for v5.6
Date: Tue, 28 Jan 2020 18:12:13 +0100 [thread overview]
Message-ID: <20200128171213.GA11313@gmail.com> (raw)
Linus,
Please pull the latest x86-boot-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86-boot-for-linus
# HEAD: dacc9092336be20b01642afe1a51720b31f60369 x86/sysfb: Fix check for bad VRAM size
Two minor changes: fix an atypical binutils combination build bug, and
also fix a VRAM size check for simplefb.
Thanks,
Ingo
------------------>
Arvind Sankar (1):
x86/sysfb: Fix check for bad VRAM size
Ilie Halip (1):
x86/boot: Discard .eh_frame sections
arch/x86/boot/setup.ld | 5 ++++-
arch/x86/kernel/sysfb_simplefb.c | 2 +-
2 files changed, 5 insertions(+), 2 deletions(-)
next reply other threads:[~2020-01-28 17:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-28 17:12 Ingo Molnar [this message]
2020-01-28 21:15 ` [GIT PULL] x86/boot changes for v5.6 pr-tracker-bot
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=20200128171213.GA11313@gmail.com \
--to=mingo@kernel.org \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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