From: Jakub Kicinski <kuba@kernel.org>
To: "Keller, Jacob E" <jacob.e.keller@intel.com>
Cc: Jiri Pirko <jiri@resnulli.us>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"davem@davemloft.net" <davem@davemloft.net>,
"idosch@nvidia.com" <idosch@nvidia.com>,
"pabeni@redhat.com" <pabeni@redhat.com>,
"edumazet@google.com" <edumazet@google.com>,
"saeedm@nvidia.com" <saeedm@nvidia.com>,
"vikas.gupta@broadcom.com" <vikas.gupta@broadcom.com>,
"gospo@broadcom.com" <gospo@broadcom.com>
Subject: Re: [patch net-next 4/4] net: devlink: expose default flash update target
Date: Fri, 19 Aug 2022 14:45:45 -0700 [thread overview]
Message-ID: <20220819144545.1efd6a04@kernel.org> (raw)
In-Reply-To: <CO1PR11MB50890139A9EEBD1AEBA54249D66C9@CO1PR11MB5089.namprd11.prod.outlook.com>
On Fri, 19 Aug 2022 20:59:28 +0000 Keller, Jacob E wrote:
> > My intuition would be that if you specify no component you're flashing
> > the entire device. Is that insufficient? Can you explain the use case?
> >
> > Also Documentation/ needs to be updated.
>
> Some of the components in ice include the DDP which has an info
> version, but which is not part of the flash but is loaded by the
> driver during initialization.
Right "entire device" as in "everything in 'stored'". Runtime loaded
stuff should not be listed in "stored" and therefore not be considered
"flashable". Correct?
next prev parent reply other threads:[~2022-08-19 21:46 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-18 13:00 [patch net-next 0/4] net: devlink: sync flash and dev info commands Jiri Pirko
2022-08-18 13:00 ` [patch net-next 1/4] net: devlink: extend info_get() version put to indicate a flash component Jiri Pirko
2022-08-18 21:23 ` Keller, Jacob E
2022-08-19 8:10 ` Jiri Pirko
2022-08-18 13:00 ` [patch net-next 2/4] net: devlink: expose the info about version representing a component Jiri Pirko
2022-08-18 13:00 ` [patch net-next 3/4] netdevsim: expose version of default flash target Jiri Pirko
2022-08-18 13:00 ` [patch net-next 4/4] net: devlink: expose default flash update target Jiri Pirko
2022-08-19 2:53 ` Jakub Kicinski
2022-08-19 8:12 ` Jiri Pirko
2022-08-19 21:54 ` Jakub Kicinski
2022-08-20 5:44 ` Jiri Pirko
2022-08-20 20:11 ` Jakub Kicinski
2022-08-19 20:59 ` Keller, Jacob E
2022-08-19 21:45 ` Jakub Kicinski [this message]
2022-08-19 22:07 ` Keller, Jacob E
2022-08-20 5:46 ` Jiri Pirko
2022-08-22 17:09 ` Keller, Jacob E
2022-08-23 6:38 ` Jiri Pirko
2022-08-18 21:16 ` [patch net-next 0/4] net: devlink: sync flash and dev info commands Keller, Jacob E
2022-08-19 2:49 ` Jakub Kicinski
2022-08-19 8:25 ` [patch net-next 0/4] net: devlink: sync flash and dev info command Jiri Pirko
2022-08-23 10:09 ` Kumar, M Chetan
2022-08-23 12:20 ` Jiri Pirko
2022-08-23 16:29 ` Kumar, M Chetan
2022-08-24 8:47 ` Jiri Pirko
2022-08-26 8:54 ` Kumar, M Chetan
2022-08-26 11:01 ` 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=20220819144545.1efd6a04@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gospo@broadcom.com \
--cc=idosch@nvidia.com \
--cc=jacob.e.keller@intel.com \
--cc=jiri@resnulli.us \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=saeedm@nvidia.com \
--cc=vikas.gupta@broadcom.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).