Netdev Archive on
help / color / mirror / Atom feed
From: Jakub Kicinski <>
To: Kalesh A P <>
	Jacob Keller <>
Subject: Re: [PATCH net-next 0/2] devlink enhancements
Date: Mon, 2 Aug 2021 09:36:22 -0700	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Mon,  2 Aug 2021 09:57:38 +0530 Kalesh A P wrote:
> From: Kalesh AP <>
> This patchset adds device capability reporting to devlink info API.
> It may be useful if we expose the device capabilities to the user
> through devlink info API.

Did you see the RFC Jake posted? That's way more palatable.

Operationally the API provided here is of little to no value 
to the user, and since it extends the "let the vendors dump custom
meaningless strings" paradigm present in devlink please expect 
major push back.

  parent reply	other threads:[~2021-08-02 16:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-02  4:27 Kalesh A P
2021-08-02  4:27 ` [PATCH net-next 1/2] devlink: add device capability reporting to devlink info API Kalesh A P
2021-08-02  4:27 ` [PATCH net-next 2/2] bnxt_en: Add device capabilities to devlink info_get cb Kalesh A P
2021-08-02 16:36 ` Jakub Kicinski [this message]
2021-08-02 19:41   ` [PATCH net-next 0/2] devlink enhancements Keller, Jacob E

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \ \ \
    --subject='Re: [PATCH net-next 0/2] devlink enhancements' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

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).