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/apic for 5.19
Date: Mon, 23 May 2022 21:16:20 +0200 [thread overview]
Message-ID: <YovdhH0QBN7csz/b@zn.tnic> (raw)
Hi Linus,
two fixes in x86/apic for 5.19, this time around.
Please pull,
thx.
---
The following changes since commit ce522ba9ef7e2d9fb22a39eb3371c0c64e2a433e:
Linux 5.18-rc2 (2022-04-10 14:21:36 -1000)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git tags/x86_apic_for_v5.19_rc1
for you to fetch changes up to 7a116a2dd32d96869f0f93bac00b900859ba0434:
x86/apic: Do apic driver probe for "nosmp" use case (2022-05-01 22:40:29 +0200)
----------------------------------------------------------------
- Always do default APIC routing setup so that cpumasks are properly
allocated and are present when later accessed ("nosmp" and x2APIC)
- Clarify the bit overlap between an old APIC and a modern, integrated one
----------------------------------------------------------------
Kuppuswamy Sathyanarayanan (1):
x86/apic: Do apic driver probe for "nosmp" use case
Thomas Gleixner (1):
x86/apic: Clarify i82489DX bit overlap in APIC_LVT0
arch/x86/include/asm/apicdef.h | 6 ------
arch/x86/kernel/apic/apic.c | 16 ++++++++++++----
2 files changed, 12 insertions(+), 10 deletions(-)
--
Regards/Gruss,
Boris.
SUSE Software Solutions Germany GmbH
GF: Ivo Totev, Andrew Myers, Andrew McDonald, Martje Boudien Moerman
(HRB 36809, AG Nürnberg)
next reply other threads:[~2022-05-23 19:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-23 19:16 Borislav Petkov [this message]
2022-05-24 2:51 ` 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=YovdhH0QBN7csz/b@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
all inboxes | Powered by JetHome®