From: Maxime Chevallier <maxime.chevallier@bootlin.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: Andrew Lunn <andrew@lunn.ch>,
davem@davemloft.net, Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>, Simon Horman <horms@kernel.org>,
Russell King <linux@armlinux.org.uk>,
Heiner Kallweit <hkallweit1@gmail.com>,
Jonathan Corbet <corbet@lwn.net>,
Shuah Khan <skhan@linuxfoundation.org>,
Oleksij Rempel <o.rempel@pengutronix.de>,
Vladimir Oltean <vladimir.oltean@nxp.com>,
Florian Fainelli <f.fainelli@gmail.com>,
thomas.petazzoni@bootlin.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH net-next] Documentation: networking: Add a test plan for ethtool pause validation
Date: Wed, 27 May 2026 08:41:16 +0200 [thread overview]
Message-ID: <43569bb0-98c1-4fc5-8b3e-c199d0c68250@bootlin.com> (raw)
In-Reply-To: <20260526172447.10ca4b9e@kernel.org>
On 5/27/26 02:24, Jakub Kicinski wrote:
> On Fri, 22 May 2026 19:51:06 +0200 Maxime Chevallier (Netdev
> Foundation) wrote:
>> Documentation/networking/pause_test_plan.rst | 556 +++++++++++++++++++
>
> It'd be great to hear from others but IMHO in the current form this is
> not suitable for Documentation/networking/ We can commit the "knowledge"
> part but enumerating the test cases seems odd for Documentation/.
I think the same, I wasn't sure exactly how/where to send that to, so at
least in this form you can generate that as a nicer to read html form,
but this will likely change given Andrew's feedback
Maxime
next prev parent reply other threads:[~2026-05-27 6:41 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-22 17:51 Maxime Chevallier (Netdev Foundation)
2026-05-27 0:24 ` Jakub Kicinski
2026-05-27 2:47 ` Andrew Lunn
2026-05-27 7:07 ` Maxime Chevallier
2026-05-27 12:08 ` Andrew Lunn
2026-05-29 1:39 ` Xuan Zhuo
2026-05-29 2:52 ` Andrew Lunn
2026-05-27 23:25 ` Jakub Kicinski
2026-05-29 7:24 ` Maxime Chevallier
2026-05-29 12:30 ` Andrew Lunn
2026-05-29 7:42 ` Maxime Chevallier
2026-05-29 7:50 ` Oleksij Rempel
2026-06-25 15:29 ` Maxime Chevallier
2026-06-25 16:12 ` Andrew Lunn
2026-06-26 8:33 ` Maxime Chevallier
2026-06-26 12:39 ` Andrew Lunn
2026-06-26 12:51 ` Maxime Chevallier
2026-06-27 0:33 ` Jakub Kicinski
2026-06-27 5:34 ` Maxime Chevallier
2026-06-27 21:30 ` Jakub Kicinski
2026-06-27 23:46 ` Andrew Lunn
2026-06-29 15:24 ` Maxime Chevallier
2026-06-29 22:40 ` Jakub Kicinski
2026-05-27 6:41 ` Maxime Chevallier [this message]
2026-05-27 3:13 ` Andrew Lunn
2026-05-28 1:15 ` Andrew Lunn
2026-05-29 8:07 ` Maxime Chevallier
2026-05-29 12:59 ` Andrew Lunn
2026-05-29 13:20 ` Maxime Chevallier
2026-06-25 10:46 ` Maxime Chevallier
2026-06-25 15:46 ` Andrew Lunn
2026-06-25 16:03 ` Maxime Chevallier
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=43569bb0-98c1-4fc5-8b3e-c199d0c68250@bootlin.com \
--to=maxime.chevallier@bootlin.com \
--cc=andrew@lunn.ch \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=hkallweit1@gmail.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=o.rempel@pengutronix.de \
--cc=pabeni@redhat.com \
--cc=skhan@linuxfoundation.org \
--cc=thomas.petazzoni@bootlin.com \
--cc=vladimir.oltean@nxp.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
Powered by JetHome