From: patchwork-bot+netdevbpf@kernel.org
To: Bastien Curutchet (Schneider Electric) <bastien.curutchet@bootlin.com>
Cc: woojung.huh@microchip.com, UNGLinuxDriver@microchip.com,
andrew@lunn.ch, olteanv@gmail.com, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
richardcochran@gmail.com, arun.ramadoss@microchip.com,
pascal.eberhard@se.com, miquel.raynal@bootlin.com,
thomas.petazzoni@bootlin.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH net v6 0/5] net: dsa: microchip: Fix resource releases in error path
Date: Tue, 25 Nov 2025 11:40:13 +0000 [thread overview]
Message-ID: <176407081300.696372.2913522306370415132.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20251120-ksz-fix-v6-0-891f80ae7f8f@bootlin.com>
Hello:
This series was applied to netdev/net.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Thu, 20 Nov 2025 10:11:59 +0100 you wrote:
> Hi all,
>
> I worked on adding PTP support for the KSZ8463. While doing so, I ran
> into a few bugs in the resource release process that occur when things go
> wrong arount IRQ initialization.
>
> This small series fixes those bugs.
>
> [...]
Here is the summary with links:
- [net,v6,1/5] net: dsa: microchip: common: Fix checks on irq_find_mapping()
https://git.kernel.org/netdev/net/c/7b3c09e16679
- [net,v6,2/5] net: dsa: microchip: ptp: Fix checks on irq_find_mapping()
https://git.kernel.org/netdev/net/c/9e059305be41
- [net,v6,3/5] net: dsa: microchip: Don't free uninitialized ksz_irq
https://git.kernel.org/netdev/net/c/25b62cc5b22c
- [net,v6,4/5] net: dsa: microchip: Free previously initialized ports on init failures
https://git.kernel.org/netdev/net/c/0f80e21bf622
- [net,v6,5/5] net: dsa: microchip: Fix symetry in ksz_ptp_msg_irq_{setup/free}()
https://git.kernel.org/netdev/net/c/d0b8fec8ae50
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:[~2025-11-25 11:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-20 9:11 [PATCH net v6 0/5] net: dsa: microchip: Fix resource releases in error path Bastien Curutchet (Schneider Electric)
2025-11-20 9:12 ` [PATCH net v6 1/5] net: dsa: microchip: common: Fix checks on irq_find_mapping() Bastien Curutchet (Schneider Electric)
2025-11-20 9:12 ` [PATCH net v6 2/5] net: dsa: microchip: ptp: " Bastien Curutchet (Schneider Electric)
2025-11-20 9:12 ` [PATCH net v6 3/5] net: dsa: microchip: Don't free uninitialized ksz_irq Bastien Curutchet (Schneider Electric)
2025-11-20 9:12 ` [PATCH net v6 4/5] net: dsa: microchip: Free previously initialized ports on init failures Bastien Curutchet (Schneider Electric)
2025-11-20 9:12 ` [PATCH net v6 5/5] net: dsa: microchip: Fix symetry in ksz_ptp_msg_irq_{setup/free}() Bastien Curutchet (Schneider Electric)
2025-11-25 11:40 ` patchwork-bot+netdevbpf [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=176407081300.696372.2913522306370415132.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=UNGLinuxDriver@microchip.com \
--cc=andrew@lunn.ch \
--cc=arun.ramadoss@microchip.com \
--cc=bastien.curutchet@bootlin.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miquel.raynal@bootlin.com \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=pabeni@redhat.com \
--cc=pascal.eberhard@se.com \
--cc=richardcochran@gmail.com \
--cc=stable@vger.kernel.org \
--cc=thomas.petazzoni@bootlin.com \
--cc=woojung.huh@microchip.com \
/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