From: Thomas Gleixner <tglx@kernel.org>
To: Sudeep Holla <sudeep.holla@kernel.org>, Marc Zyngier <maz@kernel.org>
Cc: Julian Braha <julianbraha@gmail.com>,
mark.rutland@arm.com, Sudeep Holla <sudeep.holla@kernel.org>,
lpieralisi@kernel.org, radu@rendec.net, vsethi@nvidia.com,
sdonthineni@nvidia.com, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 0/2] irqchip: gic-v3: fix unmet dependency on ARM_PSCI_FW
Date: Thu, 22 Oct 2026 23:50:12 +0200 [thread overview]
Message-ID: <877bj91k2z.ffs@fw13> (raw)
In-Reply-To: <20261021-rampant-fabulous-ant-cafccb@sudeepholla>
On Wed, Oct 21 2026 at 15:49, Sudeep Holla wrote:
> On Wed, Oct 21, 2026 at 09:27:22AM +0100, Marc Zyngier wrote:
>> On Tue, 20 Oct 2026 23:28:15 +0100,
>> Julian Braha <julianbraha@gmail.com> wrote:
>> >
>> > ARM_GIC_V3 currently selects HAVE_ARM_SMCCC_DISCOVERY without ensuring its
>> > dependency, ARM_PSCI_FW, is met.
>> >
>> > Patch 1 of this series adds stubs for arm32 so that patch 2 can make the
>> > select conditional on arm64.
>> >
>> > ---
>> > Julian Braha (2):
>> > firmware: smccc: provide stubs when discovery is disabled
>> > irqchip: gic-v3: only select HAVE_ARM_SMCCC_DISCOVERY on arm64
>> >
>> > drivers/irqchip/Kconfig | 2 +-
>> > include/linux/arm-smccc.h | 7 +++++++
>> > 2 files changed, 8 insertions(+), 1 deletion(-)
>>
>> This probably needs to go via Sudeep's tree.
>>
>
> Sure will queue it soon and send it as fixes at -rc1 or later.
Please change the subsystem prefix to "irqchip/gic-v3:" then.
Acked-by: Thomas Gleixner <tglx@kernel.org>
prev parent reply other threads:[~2026-10-22 21:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-20 22:28 Julian Braha
2026-10-20 22:28 ` [PATCH v4 1/2] firmware: smccc: provide stubs when discovery is disabled Julian Braha
2026-10-20 22:28 ` [PATCH v4 2/2] irqchip: gic-v3: only select HAVE_ARM_SMCCC_DISCOVERY on arm64 Julian Braha
2026-10-21 8:27 ` [PATCH v4 0/2] irqchip: gic-v3: fix unmet dependency on ARM_PSCI_FW Marc Zyngier
2026-10-21 14:49 ` Sudeep Holla
2026-10-22 21:50 ` Thomas Gleixner [this message]
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=877bj91k2z.ffs@fw13 \
--to=tglx@kernel.org \
--cc=julianbraha@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=mark.rutland@arm.com \
--cc=maz@kernel.org \
--cc=radu@rendec.net \
--cc=sdonthineni@nvidia.com \
--cc=sudeep.holla@kernel.org \
--cc=vsethi@nvidia.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
all inboxes | Powered by JetHome®