Netdev List
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: "Srinivasan, Vijay" <vijay.srinivasan@intel.com>
Cc: "Das, Shubham" <shubham.das@intel.com>,
	Alexander Duyck <alexander.duyck@gmail.com>,
	Lee Trager <lee@trager.us>,
	Maxime Chevallier <maxime.chevallier@bootlin.com>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"mkubecek@suse.cz" <mkubecek@suse.cz>,
	"D H, Siddaraju" <siddaraju.dh@intel.com>,
	"Chintalapalle, Balaji" <balaji.chintalapalle@intel.com>,
	"Lindberg, Magnus" <magnus.k.lindberg@ericsson.com>,
	"niklas.damberg@ericsson.com" <niklas.damberg@ericsson.com>,
	"Wirandi, Jonas" <jonas.wirandi@ericsson.com>
Subject: Re: Ethtool : PRBS feature
Date: Thu, 2 Jul 2026 00:02:28 +0200	[thread overview]
Message-ID: <26d44b09-d72c-4e23-84a6-3d0ea4a521ef@lunn.ch> (raw)
In-Reply-To: <BL3PR11MB6385517EECD04C783E9DC42488F62@BL3PR11MB6385.namprd11.prod.outlook.com>

On Wed, Jul 01, 2026 at 09:38:08PM +0000, Srinivasan, Vijay wrote:
> Hi Andrew,
> I think there is a disconnect here.

Which proves my point. The specification is not sufficient if you have
to keep correcting me.

The kAPI should be understandable by somebody who has a general
networking background. Please write a specification with that
assumption in mind. Don't assume the reader is a test engineer who has
used PRBS for half his life. Assume it is a brand new test engineer
who is hearing PRBS for the first time. That is what most engineers on
the netdev list are. Me included.

    Andrew

  reply	other threads:[~2026-07-01 22:02 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-11  9:37 Ethtool : PRBS feature Das, Shubham
2026-06-11 15:43 ` Andrew Lunn
2026-06-16 12:14   ` Das, Shubham
2026-06-16 16:14     ` Alexander H Duyck
2026-06-19 16:26       ` Das, Shubham
2026-06-19 18:37         ` Andrew Lunn
2026-06-20 13:48           ` Das, Shubham
2026-06-20 14:39             ` Maxime Chevallier
2026-06-20 19:20               ` Andrew Lunn
2026-06-22 15:10                 ` Das, Shubham
2026-06-22 15:38               ` Das, Shubham
2026-06-22 18:11                 ` Lee Trager
2026-06-23  9:43                 ` Andrew Lunn
2026-06-23 17:10                   ` Lee Trager
     [not found]                   ` <08f1b0c2-2b09-4c30-b95a-02959d409a03@trager.us>
2026-06-24  2:30                     ` Andrew Lunn
2026-06-24 15:35                       ` Alexander Duyck
2026-06-29 16:15                         ` Das, Shubham
2026-06-29 16:56                           ` Andrew Lunn
2026-07-01 17:10                             ` Das, Shubham
2026-07-01 17:32                               ` Andrew Lunn
     [not found]                                 ` <BL3PR11MB63854B0A4AA33A718D474C6588F62@BL3PR11MB6385.namprd11.prod.outlook.com>
2026-07-01 21:38                                   ` Srinivasan, Vijay
2026-07-01 22:02                                     ` Andrew Lunn [this message]
2026-07-01 23:28                                       ` Lee Trager
2026-07-01 23:15                           ` Lee Trager

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=26d44b09-d72c-4e23-84a6-3d0ea4a521ef@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=alexander.duyck@gmail.com \
    --cc=balaji.chintalapalle@intel.com \
    --cc=jonas.wirandi@ericsson.com \
    --cc=lee@trager.us \
    --cc=magnus.k.lindberg@ericsson.com \
    --cc=maxime.chevallier@bootlin.com \
    --cc=mkubecek@suse.cz \
    --cc=netdev@vger.kernel.org \
    --cc=niklas.damberg@ericsson.com \
    --cc=shubham.das@intel.com \
    --cc=siddaraju.dh@intel.com \
    --cc=vijay.srinivasan@intel.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