From: patchwork-bot+linux-riscv@kernel.org
To: <liu.xuemei1@zte.com.cn>
Cc: linux-riscv@lists.infradead.org, anup@brainfault.org,
tglx@kernel.org, pjw@kernel.org, palmer@dabbelt.com,
aou@eecs.berkeley.edu, alex@ghiti.fr, sunilvl@ventanamicro.com,
rafael.j.wysocki@intel.com, liujingqi@lanxincomputing.com,
cyan.yang@sifive.com, nick.hu@sifive.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/2] irqchip/riscv-aplic: Fix RISC-V APLIC irqchip probe issues
Date: Tue, 24 Mar 2026 06:07:33 +0000 [thread overview]
Message-ID: <177433245321.469836.8874505168992965839.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260310141349432DBRJJclgnBHYWu8it0geX@zte.com.cn>
Hello:
This series was applied to riscv/linux.git (for-next)
by Thomas Gleixner <tglx@kernel.org>:
On Tue, 10 Mar 2026 14:13:49 +0800 (CST) you wrote:
> From: Jessica Liu <liu.xuemei1@zte.com.cn>
>
> This series addresses two issues in the aplic_probe() function.
>
> Jessica Liu (2):
> irqchip/riscv-aplic: Do not clear ACPI dependencies on probe failure
> irqchip/riscv-aplic: Register syscore operations only once
>
> [...]
Here is the summary with links:
- [v2,1/2] irqchip/riscv-aplic: Do not clear ACPI dependencies on probe failure
https://git.kernel.org/riscv/c/620b6ded72a7
- [v2,2/2] irqchip/riscv-aplic: Register syscore operations only once
https://git.kernel.org/riscv/c/b330fbfd34d7
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-03-24 6:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-10 6:13 liu.xuemei1
2026-03-10 6:16 ` [PATCH v2 1/2] irqchip/riscv-aplic: Do not clear ACPI dependencies on probe failure liu.xuemei1
2026-03-10 17:43 ` [tip: irq/urgent] " tip-bot2 for Jessica Liu
2026-03-10 6:17 ` [PATCH v2 2/2] irqchip/riscv-aplic: Register syscore operations only once liu.xuemei1
2026-03-10 17:43 ` [tip: irq/urgent] " tip-bot2 for Jessica Liu
2026-03-24 6:07 ` patchwork-bot+linux-riscv [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=177433245321.469836.8874505168992965839.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=alex@ghiti.fr \
--cc=anup@brainfault.org \
--cc=aou@eecs.berkeley.edu \
--cc=cyan.yang@sifive.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=liu.xuemei1@zte.com.cn \
--cc=liujingqi@lanxincomputing.com \
--cc=nick.hu@sifive.com \
--cc=palmer@dabbelt.com \
--cc=pjw@kernel.org \
--cc=rafael.j.wysocki@intel.com \
--cc=sunilvl@ventanamicro.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
Powered by JetHome