From: Jakub Kicinski <kuba@kernel.org>
To: Parav Pandit <parav@nvidia.com>
Cc: <netdev@vger.kernel.org>, <jiri@resnulli.us>,
<davem@davemloft.net>, <edumazet@google.com>, <pabeni@redhat.com>,
<horms@kernel.org>, Shay Drory <shayd@nvidia.com>,
Mark Bloch <mbloch@nvidia.com>, Jiri Pirko <jiri@nvidia.com>
Subject: Re: [PATCH net-next] devlink: Improve the port attributes description
Date: Mon, 23 Dec 2024 10:09:55 -0800 [thread overview]
Message-ID: <20241223100955.54ceca21@kernel.org> (raw)
In-Reply-To: <20241219150158.906064-1-parav@nvidia.com>
On Thu, 19 Dec 2024 17:01:58 +0200 Parav Pandit wrote:
> Improve the description of devlink port attributes PF, VF and SF
> numbers.
Please provide more context. It's not obvious why you remove PF from
descriptions but not VF or SF.
--
pw-bot: cr
next prev parent reply other threads:[~2024-12-23 18:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-19 15:01 [PATCH net-next] devlink: Improve the port attributes description Parav Pandit
2024-12-20 17:13 ` Samudrala, Sridhar
2024-12-23 18:09 ` Jakub Kicinski [this message]
2024-12-24 3:40 ` Parav Pandit
2024-12-27 18:19 ` Jakub Kicinski
2024-12-28 3:33 ` Parav Pandit
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=20241223100955.54ceca21@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=jiri@nvidia.com \
--cc=jiri@resnulli.us \
--cc=mbloch@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=parav@nvidia.com \
--cc=shayd@nvidia.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).