All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@kernel.org>
To: Lorenzo Pieralisi <lpieralisi@kernel.org>,
	"Rafael J. Wysocki" <rafael@kernel.org>,
	Len Brown <lenb@kernel.org>, Sunil V L <sunilvl@ventanamicro.com>,
	Marc Zyngier <maz@kernel.org>,
	Huacai Chen <chenhuacai@kernel.org>,
	Anup Patel <anup@brainfault.org>,
	Hanjun Guo <guohanjun@huawei.com>,
	Sudeep Holla <sudeep.holla@kernel.org>,
	Catalin Marinas <catalin.marinas@arm.com>,
	Will Deacon <will@kernel.org>
Cc: linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
	linux-acpi@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	loongarch@lists.linux.dev,
	Lorenzo Pieralisi <lpieralisi@kernel.org>
Subject: Re: [PATCH 2/2] irqchip/gic-v5: Add IWB to ACPI probe dependency control
Date: Tue, 05 May 2026 21:58:05 +0200	[thread overview]
Message-ID: <875x51y6gi.ffs@tglx> (raw)
In-Reply-To: <20260505-gic-v5-acpi-iwb-probe-deferral-v1-2-b37b85998362@kernel.org>

On Tue, May 05 2026 at 10:48, Lorenzo Pieralisi wrote:
> On Arm GICv5 systems, wired IRQs routed to an IWB may require resolving

S/IRQs/interrupts/g

Changelogs are prose and not an acronym dump ground.

>  drivers/acpi/arm64/iort.c        | 22 +++++++++++++++++++---
>  drivers/acpi/scan.c              |  1 +
>  drivers/irqchip/irq-gic-v5-iwb.c |  5 +++++
>  drivers/irqchip/irq-gic-v5.c     | 13 +++++++++++--
>  include/linux/acpi_iort.h        |  3 ++-

I'm confused about the conglomerate of files affected by an irqchip
change...

Thanks,

        tglx

WARNING: multiple messages have this Message-ID (diff)
From: Thomas Gleixner <tglx@kernel.org>
To: Lorenzo Pieralisi <lpieralisi@kernel.org>,
	"Rafael J. Wysocki" <rafael@kernel.org>,
	Len Brown <lenb@kernel.org>, Sunil V L <sunilvl@ventanamicro.com>,
	Marc Zyngier <maz@kernel.org>,
	Huacai Chen <chenhuacai@kernel.org>,
	Anup Patel <anup@brainfault.org>,
	Hanjun Guo <guohanjun@huawei.com>,
	Sudeep Holla <sudeep.holla@kernel.org>,
	Catalin Marinas <catalin.marinas@arm.com>,
	Will Deacon <will@kernel.org>
Cc: linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
	linux-acpi@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	loongarch@lists.linux.dev,
	Lorenzo Pieralisi <lpieralisi@kernel.org>
Subject: Re: [PATCH 2/2] irqchip/gic-v5: Add IWB to ACPI probe dependency control
Date: Tue, 05 May 2026 21:58:05 +0200	[thread overview]
Message-ID: <875x51y6gi.ffs@tglx> (raw)
In-Reply-To: <20260505-gic-v5-acpi-iwb-probe-deferral-v1-2-b37b85998362@kernel.org>

On Tue, May 05 2026 at 10:48, Lorenzo Pieralisi wrote:
> On Arm GICv5 systems, wired IRQs routed to an IWB may require resolving

S/IRQs/interrupts/g

Changelogs are prose and not an acronym dump ground.

>  drivers/acpi/arm64/iort.c        | 22 +++++++++++++++++++---
>  drivers/acpi/scan.c              |  1 +
>  drivers/irqchip/irq-gic-v5-iwb.c |  5 +++++
>  drivers/irqchip/irq-gic-v5.c     | 13 +++++++++++--
>  include/linux/acpi_iort.h        |  3 ++-

I'm confused about the conglomerate of files affected by an irqchip
change...

Thanks,

        tglx

_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

  reply	other threads:[~2026-05-05 19:58 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-05  8:48 [PATCH 0/2] irqchip: Arm GICv5 IWB ACPI IRQ probe deferral Lorenzo Pieralisi
2026-05-05  8:48 ` Lorenzo Pieralisi
2026-05-05  8:48 ` [PATCH 1/2] drivers/acpi: Move RISC-V interrupt controllers autodep to ACPI IRQ code Lorenzo Pieralisi
2026-05-05  8:48   ` Lorenzo Pieralisi
2026-05-22 17:45   ` Rafael J. Wysocki
2026-05-22 17:45     ` Rafael J. Wysocki
2026-05-25  8:03     ` Lorenzo Pieralisi
2026-05-25  8:03       ` Lorenzo Pieralisi
2026-05-05  8:48 ` [PATCH 2/2] irqchip/gic-v5: Add IWB to ACPI probe dependency control Lorenzo Pieralisi
2026-05-05  8:48   ` Lorenzo Pieralisi
2026-05-05 19:58   ` Thomas Gleixner [this message]
2026-05-05 19:58     ` Thomas Gleixner
2026-05-06  8:48     ` Lorenzo Pieralisi
2026-05-06  8:48       ` Lorenzo Pieralisi

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=875x51y6gi.ffs@tglx \
    --to=tglx@kernel.org \
    --cc=anup@brainfault.org \
    --cc=catalin.marinas@arm.com \
    --cc=chenhuacai@kernel.org \
    --cc=guohanjun@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-riscv@lists.infradead.org \
    --cc=loongarch@lists.linux.dev \
    --cc=lpieralisi@kernel.org \
    --cc=maz@kernel.org \
    --cc=rafael@kernel.org \
    --cc=sudeep.holla@kernel.org \
    --cc=sunilvl@ventanamicro.com \
    --cc=will@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.