From: Willem de Bruijn <willemdebruijn.kernel@gmail.com>
To: Jakub Kicinski <kuba@kernel.org>,
Willem de Bruijn <willemdebruijn.kernel@gmail.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net,
edumazet@google.com, pabeni@redhat.com, horms@kernel.org,
andrew@lunn.ch, Willem de Bruijn <willemb@google.com>
Subject: Re: [PATCH net] selftests: drv-net: so_txtime: only send test traffic to sch_etf
Date: Fri, 07 Aug 2026 19:18:14 -0400 [thread overview]
Message-ID: <willemdebruijn.kernel.2765226ccd5ed@gmail.com> (raw)
In-Reply-To: <20260807154525.7a970468@kernel.org>
Jakub Kicinski wrote:
> On Thu, 6 Aug 2026 13:36:57 -0400 Willem de Bruijn wrote:
> > Subject: [PATCH net] selftests: drv-net: so_txtime: only send test traffic to sch_etf
>
> This should probably go to net-next - where it does not apply.
Ack, will address and send to net-next.
> I'm not sure if we documented this but selftests should not be treated
> as fixes, unless they are packaged with a kernel fix. Or you _really_
> need them in the current kernel version, but then you have to explain
> why it matters specifically to you.
No need from me. Makes total sense, but I was not aware. I do not yet
see it explicitly in maintainer-netdev.rst. If you want I can send
something like this:
@@ -66,7 +66,8 @@ driven by David Miller, the main network maintainer. There is the
``net`` tree, and the ``net-next`` tree. As you can probably guess from
the names, the ``net`` tree is for fixes to existing code already in the
mainline tree from Linus, and ``net-next`` is where the new code goes
-for the future release. You can find the trees here:
+for the future release. For selftests, all patches, including fixes,
+target net-next. You can find the trees here:
prev parent reply other threads:[~2026-08-07 23:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-06 17:36 [PATCH net] selftests: drv-net: so_txtime: only send test traffic to sch_etf Willem de Bruijn
2026-08-07 22:45 ` Jakub Kicinski
2026-08-07 23:18 ` Willem de Bruijn [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=willemdebruijn.kernel.2765226ccd5ed@gmail.com \
--to=willemdebruijn.kernel@gmail.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=willemb@google.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.