From: Jacob Keller <jacob.e.keller@intel.com>
To: Edward Cree <ecree.xilinx@gmail.com>, Jiri Pirko <jiri@resnulli.us>
Cc: <linux-net-drivers@amd.com>, <davem@davemloft.net>,
<kuba@kernel.org>, <edumazet@google.com>, <pabeni@redhat.com>,
<horms@kernel.org>, <andrew+netdev@lunn.ch>,
<habetsm.xilinx@gmail.com>, <netdev@vger.kernel.org>,
<edward.cree@amd.com>
Subject: Re: [PATCH v2 net-next 4/4] sfc: document devlink flash support
Date: Mon, 10 Feb 2025 13:11:40 -0800 [thread overview]
Message-ID: <158b8192-c33c-4ecd-a4dc-de565f05982d@intel.com> (raw)
In-Reply-To: <116cc011-4e4a-12c9-0cba-3097c6e85e0d@gmail.com>
On 2/10/2025 6:50 AM, Edward Cree wrote:
> On 10/02/2025 13:51, Jiri Pirko wrote:
>> Mon, Feb 10, 2025 at 12:25:45PM +0100, edward.cree@amd.com wrote:
>>> Info versions
>>> =============
>>> @@ -18,6 +18,10 @@ The ``sfc`` driver reports the following versions
>>> * - Name
>>> - Type
>>> - Description
>>> + * - ``fw.bundle_id``
>>
>> Why "id"? It is the bundle version, isn't it. In that case just "bundle"
>> would be fine I guess...
>
> bundle_id comes from DEVLINK_INFO_VERSION_GENERIC_FW_BUNDLE_ID in
> include/net/devlink.h, which git blame tells me was added by Jacob
> Keller in 2020 as a generalisation of a similar name in nfp.[1]
> Its use in sfc was added[2] by Alejandro Lucero in 2023 but seems to
> have been left out of the documentation at that time.
> The present patch series is merely documenting the name that already
> exists, not adding it. Changing it might break existing scripts, and
> in any case would affect more drivers than just sfc (it is used by
> i40e, ice, and nfp).
>
> CCing Jacob in case he has anything to add on why that name was chosen.
>
> [1]: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=c90977a3c227
> [2]: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=14743ddd2495
>
Yep. The versions were discussed extensively at [1] and I ultimately
settled on re-using fw.bundle_id as a generic name rather than having
nfp use bundle_id but everyone else use bundle [2]
[1]
https://lore.kernel.org/netdev/83a7a25e-50f0-862d-f535-92d64d86fd4f@intel.com/
[2]
https://lore.kernel.org/netdev/20200321081028.2763550-8-jeffrey.t.kirsher@intel.com/
I don't think we can really change this at this point given this is
effectively part of uABI.
next prev parent reply other threads:[~2025-02-10 21:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-10 11:25 [PATCH v2 net-next 0/4] sfc: support devlink flash edward.cree
2025-02-10 11:25 ` [PATCH v2 net-next 1/4] sfc: parse headers of devlink flash images edward.cree
2025-02-10 11:25 ` [PATCH v2 net-next 2/4] sfc: extend NVRAM MCDI handlers edward.cree
2025-02-10 11:25 ` [PATCH v2 net-next 3/4] sfc: deploy devlink flash images to NIC over MCDI edward.cree
2025-02-10 11:25 ` [PATCH v2 net-next 4/4] sfc: document devlink flash support edward.cree
2025-02-10 13:51 ` Jiri Pirko
2025-02-10 14:50 ` Edward Cree
2025-02-10 16:21 ` Jiri Pirko
2025-02-10 21:11 ` Jacob Keller [this message]
2025-02-12 2:00 ` [PATCH v2 net-next 0/4] sfc: support devlink flash patchwork-bot+netdevbpf
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=158b8192-c33c-4ecd-a4dc-de565f05982d@intel.com \
--to=jacob.e.keller@intel.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=ecree.xilinx@gmail.com \
--cc=edumazet@google.com \
--cc=edward.cree@amd.com \
--cc=habetsm.xilinx@gmail.com \
--cc=horms@kernel.org \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=linux-net-drivers@amd.com \
--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;
as well as URLs for NNTP newsgroup(s).