Netdev List
 help / color / mirror / Atom feed
From: Jiri Pirko <jiri@resnulli.us>
To: Vincent Mailhol <mailhol.vincent@wanadoo.fr>
Cc: Jiri Pirko <jiri@nvidia.com>, Jakub Kicinski <kuba@kernel.org>,
	"David S . Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Paolo Abeni <pabeni@redhat.com>,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	Andrew Lunn <andrew@lunn.ch>,
	Marc Kleine-Budde <mkl@pengutronix.de>,
	linux-can <linux-can@vger.kernel.org>
Subject: Re: [PATCH net-next v2] net: devlink: add DEVLINK_INFO_VERSION_GENERIC_FW_BOOTLOADER
Date: Tue, 29 Nov 2022 09:28:12 +0100	[thread overview]
Message-ID: <Y4XCnAA2hGvqgXh0@nanopsycho> (raw)
In-Reply-To: <20221129031406.3849872-1-mailhol.vincent@wanadoo.fr>

Tue, Nov 29, 2022 at 04:14:06AM CET, mailhol.vincent@wanadoo.fr wrote:
>As discussed in [1], abbreviating the bootloader to "bl" might not be
>well understood. Instead, a bootloader technically being a firmware,
>name it "fw.bootloader".
>
>Add a new macro to devlink.h to formalize this new info attribute name
>and update the documentation.
>
>[1] https://lore.kernel.org/netdev/20221128142723.2f826d20@kernel.org/
>
>Suggested-by: Jakub Kicinski <kuba@kernel.org>
>Signed-off-by: Vincent Mailhol <mailhol.vincent@wanadoo.fr>
>---
>* Changelog *
>
>v1 -> v2:
>
>  * update the documentation as well.
>  Link: https://lore.kernel.org/netdev/20221129020151.3842613-1-mailhol.vincent@wanadoo.fr/
>---
> Documentation/networking/devlink/devlink-info.rst | 5 +++++
> include/net/devlink.h                             | 2 ++
> 2 files changed, 7 insertions(+)
>
>diff --git a/Documentation/networking/devlink/devlink-info.rst b/Documentation/networking/devlink/devlink-info.rst
>index 7572bf6de5c1..1242b0e6826b 100644
>--- a/Documentation/networking/devlink/devlink-info.rst
>+++ b/Documentation/networking/devlink/devlink-info.rst
>@@ -198,6 +198,11 @@ fw.bundle_id
> 
> Unique identifier of the entire firmware bundle.
> 
>+fw.bootloader
>+-------------
>+
>+Version of the bootloader.
>+
> Future work
> ===========
> 
>diff --git a/include/net/devlink.h b/include/net/devlink.h
>index 074a79b8933f..2f552b90b5c6 100644
>--- a/include/net/devlink.h
>+++ b/include/net/devlink.h
>@@ -621,6 +621,8 @@ enum devlink_param_generic_id {
> #define DEVLINK_INFO_VERSION_GENERIC_FW_ROCE	"fw.roce"
> /* Firmware bundle identifier */
> #define DEVLINK_INFO_VERSION_GENERIC_FW_BUNDLE_ID	"fw.bundle_id"
>+/* Bootloader */
>+#define DEVLINK_INFO_VERSION_GENERIC_FW_BOOTLOADER	"fw.bootloader"

You add it and don't use it. You should add only what you use.

  reply	other threads:[~2022-11-29  8:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-29  3:14 [PATCH net-next v2] net: devlink: add DEVLINK_INFO_VERSION_GENERIC_FW_BOOTLOADER Vincent Mailhol
2022-11-29  8:28 ` Jiri Pirko [this message]
2022-11-29  9:28   ` Vincent MAILHOL
2022-11-30 17:03     ` Marc Kleine-Budde
2022-11-30 17:52       ` Vincent MAILHOL
2022-12-01  9:51         ` Marc Kleine-Budde

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=Y4XCnAA2hGvqgXh0@nanopsycho \
    --to=jiri@resnulli.us \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=jiri@nvidia.com \
    --cc=kuba@kernel.org \
    --cc=linux-can@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mailhol.vincent@wanadoo.fr \
    --cc=mkl@pengutronix.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox