From: Bastien Curutchet <bastien.curutchet@bootlin.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: Paolo Abeni <pabeni@redhat.com>,
netdev-bot+sashiko@kernel.org, woojung.huh@microchip.com,
UNGLinuxDriver@microchip.com, andrew@lunn.ch, olteanv@gmail.com,
davem@davemloft.net, edumazet@google.com,
richardcochran@gmail.com, ceggers@arri.de,
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 v2] net: dsa: microchip: save the periodic output request
Date: Fri, 25 Sep 2026 08:16:27 +0200 [thread overview]
Message-ID: <ee69ae01-97ab-470c-ba1d-658f1700463c@bootlin.com> (raw)
In-Reply-To: <20260924080252.2169c100@kernel.org>
Hi Jakub,
On 9/24/26 5:02 PM, Jakub Kicinski wrote:
> On Wed, 23 Sep 2026 08:51:19 +0200 Bastien Curutchet wrote:
>>> Also if the issue you are observing on an older kernel is already fixed in
>>> the vanilla tree, I suggest instead sending to stable the relevant change.
>>>
>> The issue isn't fixed in the vanilla tree, it's only hidden by the fact
>> that the driver doesn't register the flags it supports in
>> .supported_perout_flags.
>> And only the flag issue is hidden, the index still gets wrongly set to 0
>> on restart.
>
> - net
> - Fixes
> + net-next
> + better commit msg explaining the state of things
>
> ?
Ok, I will do it this way, thank you !
Best regards,
Bastien
prev parent reply other threads:[~2026-09-25 6:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-17 8:39 Bastien Curutchet (Schneider Electric)
2026-09-21 8:52 ` netdev-bot+sashiko
2026-09-22 6:32 ` Bastien Curutchet
2026-09-22 10:01 ` Paolo Abeni
2026-09-23 6:51 ` Bastien Curutchet
2026-09-24 15:02 ` Jakub Kicinski
2026-09-25 6:16 ` Bastien Curutchet [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=ee69ae01-97ab-470c-ba1d-658f1700463c@bootlin.com \
--to=bastien.curutchet@bootlin.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=andrew@lunn.ch \
--cc=arun.ramadoss@microchip.com \
--cc=ceggers@arri.de \
--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-bot+sashiko@kernel.org \
--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
all inboxes | Powered by JetHome®