From: Jiri Pirko <jiri@resnulli.us>
To: Jakub Kicinski <kuba@kernel.org>
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: Tue, 8 Nov 2022 14:06:34 +0100 [thread overview]
Message-ID: <Y2pUWr/LTw+4J3OS@nanopsycho> (raw)
In-Reply-To: <20221107100206.1e2f3743@kernel.org>
Mon, Nov 07, 2022 at 07:02:06PM CET, kuba@kernel.org wrote:
>On Mon, 7 Nov 2022 18:03:06 +0100 Jiri Pirko wrote:
>>> Oh, my bad. But I think the same justification applies here.
>>> Overloading the API with information with no clear use seems
>>> counter-productive to me.
>>
>> Well, it gives the user hint about what he can pass as a "component
>> name" on the cmdline. Otherwise, the user has no clue.
>
>The command line contains:
> - device
> - component (optional)
> - fw file to flash
>
>What scenario are you thinking of where the user has the file they want
>to flash, intent to flash a particular component only but does not know
>whether that component can be flashed?
No scenario. Lets drop this.
prev parent reply other threads:[~2022-11-08 13:06 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
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 [this message]
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=Y2pUWr/LTw+4J3OS@nanopsycho \
--to=jiri@resnulli.us \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--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).