From: Pavel Machek <pavel@denx.de>
To: Sasha Levin <sashal@kernel.org>
Cc: linux-kernel@vger.kernel.org, stable@vger.kernel.org,
Samuel Holland <samuel@sholland.org>,
kernel test robot <lkp@intel.com>, Marc Zyngier <maz@kernel.org>,
tglx@linutronix.de
Subject: Re: [PATCH AUTOSEL 4.19 04/16] genirq: GENERIC_IRQ_IPI depends on SMP
Date: Sat, 13 Aug 2022 15:44:22 +0200 [thread overview]
Message-ID: <20220813130448.GA23630@duo.ucw.cz> (raw)
In-Reply-To: <20220808013914.316709-4-sashal@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 704 bytes --]
Hi!
> From: Samuel Holland <samuel@sholland.org>
>
> [ Upstream commit 0f5209fee90b4544c58b4278d944425292789967 ]
>
> The generic IPI code depends on the IRQ affinity mask being allocated
> and initialized. This will not be the case if SMP is disabled. Fix up
> the remaining driver that selected GENERIC_IRQ_IPI in a non-SMP config.
Are you sure this is right thing to do on 4.19 kernel?
In particular, should we have "Only register IPI domain when SMP is
enabled" in the tree before this can be applied?
Best regards,
Pavel
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2022-08-13 13:44 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-08 1:38 [PATCH AUTOSEL 4.19 01/16] arm64: Do not forget syscall when starting a new thread Sasha Levin
2022-08-08 1:38 ` [PATCH AUTOSEL 4.19 02/16] arm64: fix oops in concurrently setting insn_emulation sysctls Sasha Levin
2022-08-08 1:39 ` [PATCH AUTOSEL 4.19 03/16] ext2: Add more validity checks for inode counts Sasha Levin
2022-08-08 1:39 ` [PATCH AUTOSEL 4.19 04/16] genirq: GENERIC_IRQ_IPI depends on SMP Sasha Levin
2022-08-13 13:44 ` Pavel Machek [this message]
2022-08-08 1:39 ` [PATCH AUTOSEL 4.19 05/16] ARM: dts: imx6ul: add missing properties for sram Sasha Levin
2022-08-08 1:39 ` [PATCH AUTOSEL 4.19 06/16] ARM: dts: imx6ul: change operating-points to uint32-matrix Sasha Levin
2022-08-08 1:39 ` [PATCH AUTOSEL 4.19 07/16] ARM: dts: imx6ul: fix lcdif node compatible Sasha Levin
2022-08-08 1:39 ` [PATCH AUTOSEL 4.19 08/16] ARM: dts: imx6ul: fix qspi " Sasha Levin
2022-08-08 1:39 ` [PATCH AUTOSEL 4.19 09/16] ARM: OMAP2+: display: Fix refcount leak bug Sasha Levin
2022-08-08 1:39 ` [PATCH AUTOSEL 4.19 10/16] ACPI: EC: Remove duplicate ThinkPad X1 Carbon 6th entry from DMI quirks Sasha Levin
2022-08-08 1:39 ` [PATCH AUTOSEL 4.19 11/16] ACPI: PM: save NVS memory for Lenovo G40-45 Sasha Levin
2022-08-08 1:39 ` [PATCH AUTOSEL 4.19 12/16] ACPI: LPSS: Fix missing check in register_device_clock() Sasha Levin
2022-08-08 1:39 ` [PATCH AUTOSEL 4.19 13/16] arm64: dts: qcom: ipq8074: fix NAND node name Sasha Levin
2022-08-08 1:39 ` [PATCH AUTOSEL 4.19 14/16] hwmon: (sht15) Fix wrong assumptions in device remove callback Sasha Levin
2022-08-08 1:39 ` [PATCH AUTOSEL 4.19 15/16] PM: hibernate: defer device probing when resuming from hibernation Sasha Levin
2022-08-08 1:39 ` [PATCH AUTOSEL 4.19 16/16] selinux: Add boundary check in put_entry() Sasha Levin
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=20220813130448.GA23630@duo.ucw.cz \
--to=pavel@denx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=maz@kernel.org \
--cc=samuel@sholland.org \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.org \
--cc=tglx@linutronix.de \
/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