public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Lorenzo Pieralisi <lpieralisi@kernel.org>
To: Thomas Gleixner <tglx@kernel.org>,
	"Rafael J. Wysocki" <rafael@kernel.org>
Cc: Len Brown <lenb@kernel.org>,
	Robert Moore <robert.moore@intel.com>,
	Hanjun Guo <guohanjun@huawei.com>,
	Sudeep Holla <sudeep.holla@arm.com>,
	Marc Zyngier <maz@kernel.org>,
	Bjorn Helgaas <bhelgaas@google.com>,
	Jonathan Cameron <jonathan.cameron@huawei.com>,
	linux-acpi@vger.kernel.org, acpica-devel@lists.linux.dev,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, linux-pci@vger.kernel.org
Subject: Re: [PATCH v3 0/6] irqchip/gic-v5: Code first ACPI boot support
Date: Mon, 19 Jan 2026 09:19:12 +0100	[thread overview]
Message-ID: <aW3pALPxn4i9fiDO@lpieralisi> (raw)
In-Reply-To: <87sec30yhk.ffs@tglx>

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@rafael.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


  reply	other threads:[~2026-01-19  8:19 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-15  9:50 [PATCH v3 0/6] irqchip/gic-v5: Code first ACPI boot support Lorenzo Pieralisi
2026-01-15  9:50 ` [PATCH v3 1/6] irqdomain: Add parent field to struct irqchip_fwid Lorenzo Pieralisi
2026-01-15 12:17   ` Jonathan Cameron
2026-01-15  9:50 ` [PATCH v3 2/6] PCI/MSI: Make the pci_msi_map_rid_ctlr_node() interface firmware agnostic Lorenzo Pieralisi
2026-01-15  9:50 ` [PATCH v3 3/6] irqchip/gic-v5: Split IRS probing into OF and generic portions Lorenzo Pieralisi
2026-01-15 12:23   ` Jonathan Cameron
2026-01-15  9:50 ` [PATCH v3 4/6] irqchip/gic-v5: Add ACPI IRS probing Lorenzo Pieralisi
2026-01-15 12:30   ` Jonathan Cameron
2026-01-15  9:50 ` [PATCH v3 5/6] irqchip/gic-v5: Add ACPI ITS probing Lorenzo Pieralisi
2026-01-15  9:50 ` [PATCH v3 6/6] irqchip/gic-v5: Add ACPI IWB probing Lorenzo Pieralisi
2026-01-18 11:00 ` [PATCH v3 0/6] irqchip/gic-v5: Code first ACPI boot support Lorenzo Pieralisi
2026-01-18 14:47   ` Thomas Gleixner
2026-01-19  8:19     ` Lorenzo Pieralisi [this message]
2026-01-19 13:54       ` Thomas Gleixner
2026-01-20 10:16         ` Lorenzo Pieralisi
2026-01-23  8:42           ` Lorenzo Pieralisi
2026-01-26 20:42             ` Rafael J. Wysocki
2026-01-27 14:34               ` Rafael J. Wysocki

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=aW3pALPxn4i9fiDO@lpieralisi \
    --to=lpieralisi@kernel.org \
    --cc=acpica-devel@lists.linux.dev \
    --cc=bhelgaas@google.com \
    --cc=guohanjun@huawei.com \
    --cc=jonathan.cameron@huawei.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=maz@kernel.org \
    --cc=rafael@kernel.org \
    --cc=robert.moore@intel.com \
    --cc=sudeep.holla@arm.com \
    --cc=tglx@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