From: Nicolai Buchwitz <nb@tipi-net.de>
To: "Andrew Lunn" <andrew@lunn.ch>,
"Sébastien Royen" <sebastien.royen@armadeus.com>
Cc: netdev-bot+sinfo@kernel.org,
Woojung Huh <woojung.huh@microchip.com>,
netdev@vger.kernel.org
Subject: Re: [PATCH net] net: dsa: microchip: fix KSZ8765 fiber detection
Date: Tue, 06 Oct 2026 18:21:52 +0200 [thread overview]
Message-ID: <317F33BB-1739-47AE-9107-F8FF3AE8B370@tipi-net.de> (raw)
In-Reply-To: <027573f7-b768-45df-8368-6dcd4700e999@lunn.ch>
Hi Andrew
On October 6, 2026 6:16:02 PM GMT+02:00, Andrew Lunn <andrew@lunn.ch> wrote:
>> This issue was discovered when upgrading an embedded device from kernel 5.10 to 6.16.
>
>So is this a regression?
>
>If it is, please take a read of:
>
>https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html
>
>and consider if this should be backported to stable.
>
>You then need to set the tree as 'net'
I might be overlooking something, but the target tree is already net?
>
>https://www.kernel.org/doc/html/latest/process/maintainer-netdev.html
>
> Andrew
>
Regards
Nicolai
next prev parent reply other threads:[~2026-10-06 16:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-06 13:00 [PATCH net] net: dsa: microchip: fix KSZ8765 fiber detection Sebastien Royen
2026-10-06 14:20 ` netdev-bot+sinfo
2026-10-06 14:48 ` Sébastien Royen
2026-10-06 16:16 ` Andrew Lunn
2026-10-06 16:21 ` Nicolai Buchwitz [this message]
2026-10-06 18:24 ` Andrew Lunn
2026-10-06 21:28 ` Nicolai Buchwitz
2026-10-07 8:05 ` [PATCH net v2] " Sebastien Royen
2026-10-07 8:14 ` Nicolai Buchwitz
2026-10-07 14:10 ` netdev-bot+sinfo
2026-10-08 17:50 ` patchwork-bot+netdevbpf
2026-10-07 14:18 ` [PATCH net] " netdev-bot+sashiko
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=317F33BB-1739-47AE-9107-F8FF3AE8B370@tipi-net.de \
--to=nb@tipi-net.de \
--cc=andrew@lunn.ch \
--cc=netdev-bot+sinfo@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sebastien.royen@armadeus.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