mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Hanjun Guo <guohanjun@huawei.com>
To: Kazuhiro Abe <fj1078ii@aa.jp.fujitsu.com>,
	Lorenzo Pieralisi <lpieralisi@kernel.org>,
	Will Deacon <will@kernel.org>,
	Sudeep Holla <sudeep.holla@arm.com>,
	"Rafael J. Wysocki" <rafael@kernel.org>,
	Len Brown <lenb@kernel.org>,
	Ilkka Koskinen <ilkka@os.amperecomputing.com>,
	Catalin Marinas <catalin.marinas@arm.com>,
	<linux-acpi@vger.kernel.org>,
	<linux-arm-kernel@lists.infradead.org>,
	<linux-kernel@vger.kernel.org>,
	Koichi Okuno <fj2767dz@aa.jp.fujitsu.com>
Subject: Re: [PATCH v6] ACPI: AGDI: Add interrupt signaling mode support
Date: Thu, 8 Jan 2026 17:46:56 +0800	[thread overview]
Message-ID: <fc3fec3c-651a-f64e-e62a-3a49c2d22c9d@huawei.com> (raw)
In-Reply-To: <20260108075636.524722-1-fj1078ii@aa.jp.fujitsu.com>

On 2026/1/8 15:56, Kazuhiro Abe wrote:
> AGDI has two types of signaling modes: SDEI and interrupt.
> Currently, the AGDI driver only supports SDEI.
> Therefore, add support for interrupt signaling mode.
> The interrupt vector is retrieved from the AGDI table, and call panic
> function when an interrupt occurs.
> 
> Acked-by: Hanjun Guo <guohanjun@huawei.com>
> Reviewed-by: Ilkka Koskinen <ilkka@os.amperecomputing.com>
> Signed-off-by: Kazuhiro Abe <fj1078ii@aa.jp.fujitsu.com>
> 
> ---
> This patch (v6) has been rebased to align with the 6.19-rc4 release.
> There are no functional changes since v4.
> It has been tested and confirmed to work without issues.
> Please let us know if you have any questions or concerns.
> Thank you, Will, for taking care of the mistake in v5.
> 
> v5->v6
>   - Rebase to 6.19-rc4.
>   - Correct the mistake in v5.

Take a review again, and the mistake is gone.

Thanks
Hanjun

  reply	other threads:[~2026-01-08  9:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-08  7:56 Kazuhiro Abe
2026-01-08  9:46 ` Hanjun Guo [this message]
2026-01-08 22:29 ` Will Deacon
2026-01-09  2:15   ` Kazuhiro Abe (Fujitsu)

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=fc3fec3c-651a-f64e-e62a-3a49c2d22c9d@huawei.com \
    --to=guohanjun@huawei.com \
    --cc=catalin.marinas@arm.com \
    --cc=fj1078ii@aa.jp.fujitsu.com \
    --cc=fj2767dz@aa.jp.fujitsu.com \
    --cc=ilkka@os.amperecomputing.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=lpieralisi@kernel.org \
    --cc=rafael@kernel.org \
    --cc=sudeep.holla@arm.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 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®