linux-kernel - Re: [PATCH v3 0/6] irqchip/gic-v5: Code first ACPI boot support

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <aW3pALPxn4i9fiDO@lpieralisi>
Date: Mon, 19 Jan 2026 09:19:12 +0100
From: Lorenzo Pieralisi <lpieralisi@...nel.org>
To: Thomas Gleixner <tglx@...nel.org>,
	"Rafael J. Wysocki" <rafael@...nel.org>
Cc: Len Brown <lenb@...nel.org>, Robert Moore <robert.moore@...el.com>,
	Hanjun Guo <guohanjun@...wei.com>,
	Sudeep Holla <sudeep.holla@....com>, Marc Zyngier <maz@...nel.org>,
	Bjorn Helgaas <bhelgaas@...gle.com>,
	Jonathan Cameron <jonathan.cameron@...wei.com>,
	linux-acpi@...r.kernel.org, acpica-devel@...ts.linux.dev,
	linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
	linux-pci@...r.kernel.org
Subject: Re: [PATCH v3 0/6] irqchip/gic-v5: Code first ACPI boot support

On Sun, Jan 18, 2026 at 03:47:03PM +0100, Thomas Gleixner wrote:
> On Sun, Jan 18 2026 at 12:00, Lorenzo Pieralisi wrote:
> > I have noticed you pulled this seris into tip (thanks !) - there
> > is a strict dependency on ACPICA patches in [6] though as I tried
> > to convey with the paragraph above and dependencies below:
> >
> > prerequisite-message-id: <12822121.O9o76ZdvQC@...ael.j.wysocki>
> 
> Duh. I completely missed that.
> 
> > I don't know what's best/easier to handle this dependency but it is there,
> > I don't want it to cause you any trouble so I reported it as soon
> > as I noticed.
> 
> I zap it from my tree for now until that's sorted.

Hi Rafael,

I think the simplest way to sort this out is for this series to go via
the ACPI tree if that's OK for Thomas, given that the ACPICA code will
go via the ACPI tree anyway and there are other dependencies on it there
I assume (this series is fairly self-contained).

Or I can hack together a patch that provides the ACPICA structs needed in an
irqchip header file, conditional on the ACPICA version, add it to this series
and remove it at 7.0-rc1, it does not make much sense to create this churn
given that ACPICA code will be merged this cycle but it is doable.

Please let me know how we can handle it.

Thanks both !
Lorenzo