netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Yohei Kojima <yk@y-koj.net>
To: Andrew Lunn <andrew@lunn.ch>
Cc: Jakub Kicinski <kuba@kernel.org>,
	Andrew Lunn <andrew+netdev@lunn.ch>,
	"David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Paolo Abeni <pabeni@redhat.com>, Breno Leitao <leitao@debian.org>,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net 1/5] net: netdevsim: fix inconsistent carrier state after link/unlink
Date: Wed, 31 Dec 2025 01:20:43 +0900	[thread overview]
Message-ID: <aVP72wedMbegkqzs@desktop.homenetwork> (raw)
In-Reply-To: <1c8edd12-0933-4aae-8af3-307b133dce27@lunn.ch>

On Tue, Dec 30, 2025 at 12:02:22PM +0100, Andrew Lunn wrote:
> > Thank you for the quick reply. I don't intend for this patch to be
> > backported to the stable tree. My understanding was that bugfix patches
> > to the net tree should have Fixes: tag for historical tracking.
> > 
> > > 
> > > netdevsim is not a real device. Do its bugs actually bother people?
> > 
> > This patch fixes a real bug that is seen when a developer tries to test
> > TFO or netdevsim tests on NetworkManager-enabled systems: it causes
> > false positives in kselftests on such systems.
> 
> O.K, then keep the Fixes tag and submit it for net. However, the tests
> should be considered development work, and submitted to net-next, if
> they are not fixes. Please split this into two series.

Sure, I've submitted the v2 patch here.

https://lore.kernel.org/netdev/cover.1767108538.git.yk@y-koj.net/

Following your suggestion, I've removed the unrelated TFO tests and
the netdevsim test improvement. I will post the removed patches as a
separate series once net-next reopens.

However, I kept the regression test for this patch in the v2 series, as
the "1.5.10. Co-posting selftests" section in the maintainer-netdev
document says:

  Selftests should be part of the same series as the code changes.
  Specifically for fixes both code change and related test should
  go into the same tree (the tests may lack a Fixes tag, which is
  expected). Mixing code changes and test changes in a single commit
  is discouraged.

> 
> https://www.kernel.org/doc/html/latest/process/maintainer-netdev.html
> 
>     Andrew

Thank you,
Yohei Kojima

> 
> ---
> pw-bot: cr

  reply	other threads:[~2025-12-30 16:20 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-29 18:32 [PATCH net 0/5] net: netdevsim: fix inconsistent carrier state after link/unlink yk
2025-12-29 18:32 ` [PATCH net 1/5] " yk
2025-12-29 18:39   ` Andrew Lunn
2025-12-29 19:56     ` Yohei Kojima
2025-12-30 11:02       ` Andrew Lunn
2025-12-30 16:20         ` Yohei Kojima [this message]
2025-12-30 18:38           ` Andrew Lunn
2025-12-30 18:44             ` Yohei Kojima
2025-12-29 18:32 ` [PATCH net 2/5] selftests: netdevsim: test that linking already-connected devices fails yk
2025-12-29 18:32 ` [PATCH net 3/5] selftests: netdevsim: add carrier state consistency test yk
2025-12-29 18:32 ` [PATCH net 4/5] selftests: net: improve error handling in TFO test yk
2025-12-29 18:32 ` [PATCH net 5/5] selftests: net: report SKIP if TFO test processes timed out yk

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=aVP72wedMbegkqzs@desktop.homenetwork \
    --to=yk@y-koj.net \
    --cc=andrew+netdev@lunn.ch \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=kuba@kernel.org \
    --cc=leitao@debian.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.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;
as well as URLs for NNTP newsgroup(s).