From: Jakub Kicinski <kuba@kernel.org>
To: Jiri Pirko <jiri@resnulli.us>
Cc: netdev@vger.kernel.org, davem@davemloft.net, pabeni@redhat.com,
edumazet@google.com
Subject: Re: [patch net-next] net: devlink: expose the info about version representing a component
Date: Fri, 4 Nov 2022 19:25:10 -0700 [thread overview]
Message-ID: <20221104192510.32193898@kernel.org> (raw)
In-Reply-To: <20221104152425.783701-1-jiri@resnulli.us>
On Fri, 4 Nov 2022 16:24:25 +0100 Jiri Pirko wrote:
> If certain version exposed by a driver is marked to be representing a
> component, expose this info to the user.
>
> Example:
> $ devlink dev info
> netdevsim/netdevsim10:
> driver netdevsim
> versions:
> running:
> fw.mgmt 10.20.30
> flash_components:
> fw.mgmt
Didn't I complain that this makes no practical sense because
user needs to know what file to flash, to which component?
Or was that a different flag that I was complaining about?
> diff --git a/include/uapi/linux/devlink.h b/include/uapi/linux/devlink.h
> index 2f24b53a87a5..7f2874189188 100644
> --- a/include/uapi/linux/devlink.h
> +++ b/include/uapi/linux/devlink.h
> @@ -607,6 +607,8 @@ enum devlink_attr {
>
> DEVLINK_ATTR_SELFTESTS, /* nested */
>
> + DEVLINK_ATTR_INFO_VERSION_IS_COMPONENT, /* u8 0 or 1 */
In the interest of fairness I should complain about the use of u8/u16
devlink is genetlink so user will know kernel supports the attribute
(by looking at family->maxattr). So this can be a flag.
next prev parent reply other threads:[~2022-11-05 2:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-04 15:24 [patch net-next] net: devlink: expose the info about version representing a component Jiri Pirko
2022-11-05 2:25 ` Jakub Kicinski [this message]
2022-11-05 9:26 ` Jiri Pirko
2022-11-07 16:52 ` Jakub Kicinski
2022-11-07 17:03 ` Jiri Pirko
2022-11-07 18:02 ` Jakub Kicinski
2022-11-08 13:06 ` Jiri Pirko
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=20221104192510.32193898@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jiri@resnulli.us \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.