public inbox for netdev@vger.kernel.org 
 help / color / mirror / Atom feed
From: Jiri Pirko <jiri@resnulli•us>
To: Ido Schimmel <idosch@idosch•org>
Cc: Andrew Lunn <andrew@lunn•ch>,
	netdev@vger•kernel.org, davem@davemloft•net, kuba@kernel•org,
	jiri@mellanox•com, danieller@mellanox•com, mlxsw@mellanox•com,
	michael.chan@broadcom•com, jeffrey.t.kirsher@intel•com,
	saeedm@mellanox•com, leon@kernel•org, snelson@pensando•io,
	drivers@pensando•io, vivien.didelot@gmail•com,
	f.fainelli@gmail•com, Ido Schimmel <idosch@mellanox•com>
Subject: Re: [PATCH net-next 3/3] selftests: net: Add port split test
Date: Wed, 20 May 2020 15:53:46 +0200	[thread overview]
Message-ID: <20200520135346.GA2478@nanopsycho> (raw)
In-Reply-To: <20200520134340.GA1050786@splinter>

Wed, May 20, 2020 at 03:43:40PM CEST, idosch@idosch•org wrote:
>On Tue, May 19, 2020 at 09:33:06PM +0200, Andrew Lunn wrote:
>> > It's basically the number of lanes
>> 
>> Then why not call it lanes? It makes it clearer how this maps to the
>> hardware?
>
>I'm not against it. We discussed it and decided to go with width. Jiri /
>Danielle, are you OK with changing to lanes?

Sure, no problem.

  reply	other threads:[~2020-05-20 13:53 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-19 13:40 [PATCH net-next 0/3] devlink: Add port width attribute Ido Schimmel
2020-05-19 13:40 ` [PATCH net-next 1/3] mlxsw: Set port width attribute in driver Ido Schimmel
2020-05-19 13:40 ` [PATCH net-next 2/3] devlink: Add a new devlink port width attribute and pass to netlink Ido Schimmel
2020-05-19 19:24   ` Shannon Nelson
2020-05-19 13:40 ` [PATCH net-next 3/3] selftests: net: Add port split test Ido Schimmel
2020-05-19 14:15   ` Andrew Lunn
2020-05-19 18:56     ` Ido Schimmel
2020-05-19 19:33       ` Andrew Lunn
2020-05-20 13:43         ` Ido Schimmel
2020-05-20 13:53           ` Jiri Pirko [this message]
2020-05-20 15:23             ` Danielle Ratson
2020-05-22  0:03 ` [PATCH net-next 0/3] devlink: Add port width attribute David Miller

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=20200520135346.GA2478@nanopsycho \
    --to=jiri@resnulli$(echo .)us \
    --cc=andrew@lunn$(echo .)ch \
    --cc=danieller@mellanox$(echo .)com \
    --cc=davem@davemloft$(echo .)net \
    --cc=drivers@pensando$(echo .)io \
    --cc=f.fainelli@gmail$(echo .)com \
    --cc=idosch@idosch$(echo .)org \
    --cc=idosch@mellanox$(echo .)com \
    --cc=jeffrey.t.kirsher@intel$(echo .)com \
    --cc=jiri@mellanox$(echo .)com \
    --cc=kuba@kernel$(echo .)org \
    --cc=leon@kernel$(echo .)org \
    --cc=michael.chan@broadcom$(echo .)com \
    --cc=mlxsw@mellanox$(echo .)com \
    --cc=netdev@vger$(echo .)kernel.org \
    --cc=saeedm@mellanox$(echo .)com \
    --cc=snelson@pensando$(echo .)io \
    --cc=vivien.didelot@gmail$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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