mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: patchwork-bot+linux-riscv@kernel.org
To: Nick Hu <nick.hu@sifive.com>
Cc: linux-riscv@lists.infradead.org, anup@brainfault.org,
	tglx@linutronix.de, pjw@kernel.org, palmer@dabbelt.com,
	aou@eecs.berkeley.edu, alex@ghiti.fr,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] irqchip/riscv-intc: Fix missing .free callback for freeing local IRQs
Date: Fri, 19 Dec 2025 08:10:11 +0000	[thread overview]
Message-ID: <176613181132.3684357.15703370442701367735.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20251114-rv-intc-fix-v1-1-a3edd1c1a868@sifive.com>

Hello:

This patch was applied to riscv/linux.git (fixes)
by Thomas Gleixner <tglx@linutronix.de>:

On Fri, 14 Nov 2025 15:28:44 +0800 you wrote:
> The irq_domain_free_irqs() helper requires that the irq_domain_ops->free
> callback be implemented. Otherwise, the kernel reports the warning
> message "NULL pointer, cannot free irq" when the user calls
> irq_dispose_mapping() to release the per-HART local IRQs.
> 
> Set the irq_domain_ops->free to irq_domain_free_irqs_top() to free the
> IRQs.
> 
> [...]

Here is the summary with links:
  - irqchip/riscv-intc: Fix missing .free callback for freeing local IRQs
    https://git.kernel.org/riscv/c/14473a1f8859

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2025-12-19  8:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-14  7:28 Nick Hu
2025-11-14 15:56 ` [tip: irq/urgent] irqchip/riscv-intc: Add missing free() callback in riscv_intc_domain_ops tip-bot2 for Nick Hu
2025-12-19  8:10 ` 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=176613181132.3684357.15703370442701367735.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=nick.hu@sifive.com \
    --cc=palmer@dabbelt.com \
    --cc=pjw@kernel.org \
    --cc=tglx@linutronix.de \
    /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