From: "Christophe Leroy (CS GROUP)" <chleroy@kernel.org>
To: Ioana Ciornei <ioana.ciornei@nxp.com>, Myeonghun Pak <mhun512@gmail.com>
Cc: Christophe Leroy <chleroy@kernel.org>,
linux-kernel@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
linux-arm-kernel@lists.infradead.org,
Ijae Kim <ae878000@gmail.com>,
stable@vger.kernel.org
Subject: Re: [PATCH v2 0/2] soc: fsl: dpio: Fix IRQ cleanup during probe and removal
Date: Mon, 5 Oct 2026 12:43:20 +0200 [thread overview]
Message-ID: <179119699110.180542.13258001668157935133.b4-ty@kernel.org> (raw)
In-Reply-To: <20261002194802.375497-1-mhun512@gmail.com>
On Fri, 02 Oct 2026 15:48:00 -0400, Myeonghun Pak wrote:
> This series fixes two DPIO I/O object lifetime issues during probe
> failure and device removal.
>
> Patch 1 releases the I/O object when IRQ registration fails and removes
> the unnecessary unregister call from the probe error path. Patch 2 frees
> the managed IRQ before returning its resource to the MC pool and before
> releasing the I/O object during removal.
>
> [...]
Applied, thanks!
[1/2] soc: fsl: dpio: Fix cleanup on IRQ registration failure
commit: 899559907f9d8bce0720f6d4336b2871e83957ae
[2/2] soc: fsl: dpio: Free the IRQ before releasing the I/O object
commit: c4ddf1eb1d321e40d82fb89d34b61edb3f927198
Best regards,
--
Christophe Leroy (CS GROUP) <chleroy@kernel.org>
prev parent reply other threads:[~2026-10-05 10:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-02 19:48 [PATCH v2 0/2] soc: fsl: dpio: Fix IRQ cleanup during probe and removal Myeonghun Pak
2026-10-02 19:48 ` [PATCH v2 1/2] soc: fsl: dpio: Fix cleanup on IRQ registration failure Myeonghun Pak
2026-10-02 19:48 ` [PATCH v2 2/2] soc: fsl: dpio: Free the IRQ before releasing the I/O object Myeonghun Pak
2026-10-05 7:42 ` [PATCH v2 0/2] soc: fsl: dpio: Fix IRQ cleanup during probe and removal Ioana Ciornei
2026-10-05 10:43 ` Christophe Leroy (CS GROUP) [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=179119699110.180542.13258001668157935133.b4-ty@kernel.org \
--to=chleroy@kernel.org \
--cc=ae878000@gmail.com \
--cc=ioana.ciornei@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mhun512@gmail.com \
--cc=stable@vger.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