From: Borislav Petkov <bp@suse.de>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: x86-ml <x86@kernel.org>, lkml <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] x86/cleanups updates for v5.10
Date: Mon, 12 Oct 2020 12:54:11 +0200 [thread overview]
Message-ID: <20201012105411.GI25311@zn.tnic> (raw)
Hi Linus,
please pull maybe the easiest branch of all. :-)
Thx.
---
The following changes since commit d012a7190fc1fd72ed48911e77ca97ba4521bccd:
Linux 5.9-rc2 (2020-08-23 14:08:43 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git tags/x86_cleanups_for_v5.10
for you to fetch changes up to 900ffe39fec908e0aa26a30612e43ebc7140db79:
x86/entry: Fix typo in comments for syscall_enter_from_user_mode() (2020-09-22 18:24:46 +0200)
----------------------------------------------------------------
* Misc minor cleanups.
----------------------------------------------------------------
Colin Ian King (1):
x86/resctrl: Fix spelling in user-visible warning messages
Kees Cook (1):
x86/entry: Fix typo in comments for syscall_enter_from_user_mode()
Uros Bizjak (1):
x86/entry/64: Do not include inst.h in calling.h
Wang Hai (1):
x86/mpparse: Remove duplicate io_apic.h include
arch/x86/entry/calling.h | 1 -
arch/x86/kernel/cpu/resctrl/core.c | 4 ++--
arch/x86/kernel/mpparse.c | 1 -
include/linux/entry-common.h | 2 +-
kernel/entry/common.c | 2 +-
5 files changed, 4 insertions(+), 6 deletions(-)
--
Regards/Gruss,
Boris.
SUSE Software Solutions Germany GmbH, GF: Felix Imendörffer, HRB 36809, AG Nürnberg
next reply other threads:[~2020-10-12 10:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-12 10:54 Borislav Petkov [this message]
2020-10-12 18:21 ` [GIT PULL] x86/cleanups updates for v5.10 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=20201012105411.GI25311@zn.tnic \
--to=bp@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--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