From: patchwork-bot+linux-riscv@kernel.org
To: Prajwal N <prajwal.n@oss.qualcomm.com>
Cc: linux-riscv@lists.infradead.org, anup@brainfault.org,
tglx@kernel.org, radu@rendec.net, pjw@kernel.org,
palmer@dabbelt.com, aou@eecs.berkeley.edu, alex@ghiti.fr,
linux-kernel@vger.kernel.org, prajwal.n.oss@gmail.com
Subject: Re: [PATCH] irqchip: riscv-imsic: Expose the fwnode via the global config
Date: Sun, 01 Nov 2026 22:16:16 +0000 [thread overview]
Message-ID: <179357137690.2624073.10590886013198507782.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261002120417.2708979-1-prajwal.n@oss.qualcomm.com>
Hello:
This patch was applied to riscv/linux.git (fixes)
by Thomas Gleixner <tglx@kernel.org>:
On Fri, 2 Oct 2026 17:34:17 +0530 you wrote:
> The fwnode describes a global property of the IMSIC interrupt
> controller that is equally relevant to external consumers of
> imsic_global_config as it is to the imsic_priv itself.
>
> Keeping it in imsic_priv forces the external drivers to access
> the private structure rather than using the already exported
> imsic_get_global_config() interface.
>
> [...]
Here is the summary with links:
- irqchip: riscv-imsic: Expose the fwnode via the global config
https://git.kernel.org/riscv/c/ff6f8cd2919b
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-11-01 22:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-02 12:04 Prajwal N
2026-10-02 17:06 ` Anup Patel
2026-10-15 10:22 ` [tip: irq/drivers] irqchip/riscv-imsic: " tip-bot2 for Prajwal N
2026-11-01 22:16 ` 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=179357137690.2624073.10590886013198507782.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=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=pjw@kernel.org \
--cc=prajwal.n.oss@gmail.com \
--cc=prajwal.n@oss.qualcomm.com \
--cc=radu@rendec.net \
--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
all inboxes | Powered by JetHome®