From: Jacob Keller <jacob.e.keller@intel.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [PATCH 7/8] ice: add basic handler for devlink .info_get
Date: Wed, 11 Mar 2020 18:07:36 -0700 [thread overview]
Message-ID: <a4fd8740-54f0-0e83-7aba-aad715fc2af1@intel.com> (raw)
In-Reply-To: <20200311165057.3f69e090@kicinski-fedora-PC1C0HJN>
On 3/11/2020 4:50 PM, Jakub Kicinski wrote:
> On Wed, 11 Mar 2020 14:33:18 -0700 Jacob Keller wrote:
>> + * - ``fw.bundle``
>> + - running
>> + - 0x80002ec0
>> + - Unique identifier of the firmware image file that was loaded onto
>> + the device. Also referred to as the EETRACK identifier of the NVM.
>
> Ugh, I think I mislead you in the previous discussion..
>
> Could you s/fw.bundle/fw.bundle_id/ and make it generic? NFP has the
> "_id" at the end which I clearly forgot about..
>
Sure thing, I hadn't noticed that either. Will do.
Thanks,
Jake
next prev parent reply other threads:[~2020-03-12 1:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-11 21:33 [Intel-wired-lan] [PATCH 0/8] ice devlink support Jacob Keller
2020-03-11 21:33 ` [Intel-wired-lan] [PATCH 1/8] ice: use __le16 types for explicitly Little Endian values Jacob Keller
2020-03-11 21:33 ` [Intel-wired-lan] [PATCH 2/8] ice: create function to read a section of the NVM and Shadow RAM Jacob Keller
2020-03-11 21:33 ` [Intel-wired-lan] [PATCH 3/8] ice: store NVM version info in extracted format Jacob Keller
2020-03-11 21:33 ` [Intel-wired-lan] [PATCH 4/8] ice: discover and store size of available flash Jacob Keller
2020-03-11 21:33 ` [Intel-wired-lan] [PATCH 5/8] ice: implement full NVM read from ETHTOOL_GEEPROM Jacob Keller
2020-03-11 21:33 ` [Intel-wired-lan] [PATCH 6/8] ice: enable initial devlink support Jacob Keller
2020-03-11 21:33 ` [Intel-wired-lan] [PATCH 7/8] ice: add basic handler for devlink .info_get Jacob Keller
2020-03-11 23:50 ` Jakub Kicinski
2020-03-12 1:07 ` Jacob Keller [this message]
2020-03-11 21:33 ` [Intel-wired-lan] [PATCH 8/8] ice: add board identifier info to " Jacob Keller
2020-03-11 23:49 ` Jakub Kicinski
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=a4fd8740-54f0-0e83-7aba-aad715fc2af1@intel.com \
--to=jacob.e.keller@intel.com \
--cc=intel-wired-lan@osuosl.org \
/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