From: Maxime Chevallier <maxime.chevallier@bootlin.com>
To: "Bastien Curutchet (Schneider Electric)"
<bastien.curutchet@bootlin.com>,
Woojung Huh <woojung.huh@microchip.com>,
UNGLinuxDriver@microchip.com, Andrew Lunn <andrew@lunn.ch>,
Vladimir Oltean <olteanv@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Richard Cochran <richardcochran@gmail.com>
Cc: "Pascal Eberhard" <pascal.eberhard@se.com>,
"Miquèl Raynal" <miquel.raynal@bootlin.com>,
"Thomas Petazzoni" <thomas.petazzoni@bootlin.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net 0/3] net: dsa: microchip: Fix resource releases in error path
Date: Fri, 31 Oct 2025 17:36:07 +0100 [thread overview]
Message-ID: <b7bd5e55-1e49-49be-a298-3a92d21a6567@bootlin.com> (raw)
In-Reply-To: <20251031-ksz-fix-v1-0-7e46de999ed1@bootlin.com>
Hi Bastien,
On 31/10/2025 17:05, Bastien Curutchet (Schneider Electric) 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.
>
> The next series, which will add the PTP support, depend on this one.
>
This series targets -net, however all the patches are missing a Fixes:
tag :(
You'll need to add them for the next revision :)
Maxime
prev parent reply other threads:[~2025-10-31 16:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-31 16:05 Bastien Curutchet (Schneider Electric)
2025-10-31 16:05 ` [PATCH net 1/3] net: dsa: microchip: Fix checks on irq_find_mapping() Bastien Curutchet (Schneider Electric)
2025-10-31 16:05 ` [PATCH net 2/3] net: dsa: microchip: Ensure a ksz_irq is initialized before freeing it Bastien Curutchet (Schneider Electric)
2025-10-31 16:05 ` [PATCH net 3/3] net: dsa: microchip: Immediately assing IRQ numbers Bastien Curutchet (Schneider Electric)
2025-10-31 16:36 ` Maxime Chevallier [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=b7bd5e55-1e49-49be-a298-3a92d21a6567@bootlin.com \
--to=maxime.chevallier@bootlin.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=andrew@lunn.ch \
--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=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
all inboxes | Powered by JetHome®