All of lore.kernel.org
 help / color / mirror / Atom feed
From: Brelinski, TonyX <tonyx.brelinski@intel.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [PATCH net] ice: do not abort devlink info if PBA can't be found
Date: Mon, 21 Jun 2021 22:12:03 +0000	[thread overview]
Message-ID: <SJ0PR11MB5662931B7D5F0E3C1A628D4AFA0A9@SJ0PR11MB5662.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20210615201420.2001937-1-jacob.e.keller@intel.com>

> -----Original Message-----
> From: Intel-wired-lan <intel-wired-lan-bounces@osuosl.org> On Behalf Of
> Jacob Keller
> Sent: Tuesday, June 15, 2021 1:14 PM
> To: Intel Wired LAN <intel-wired-lan@lists.osuosl.org>
> Subject: [Intel-wired-lan] [PATCH net] ice: do not abort devlink info if PBA
> can't be found
> 
> The devlink dev info command reports version information about the device
> and firmware running on the board. This includes the "board.id"
> field which is supposed to represent an identifier of the board design.
> The ice driver uses the Product Board Assembly identifier for this.
> 
> In some cases, the PBA is not present in the NVM. If this happens, devlink
> dev info will fail with an error. Instead, modify the ice_info_pba function to
> just exit without filling in the context buffer. This will cause the board.id field
> to be skipped. Log a dev_dbg message in case someone wants to confirm
> why board.id is not showing up for them.
> 
> While at it, notice that none of the getter/fallback() functions report an error
> anymore. Convert the interface to a void so that it is no longer possible to
> add a version field that is fatal. This makes sense, because we should not fail
> to report other versions just because one of the version pieces could not be
> found.
> 
> Finally, clean up the getter functions line wrapping so that none of them take
> more than 80 columns, as is the usual style for networking files.
> 
> Signed-off-by: Jacob Keller <jacob.e.keller@intel.com>
> ---
>  drivers/net/ethernet/intel/ice/ice_devlink.c | 137 +++++++------------
>  1 file changed, 53 insertions(+), 84 deletions(-)

Tested-by: Tony Brelinski <tonyx.brelinski@intel.com> (A Contingent Worker at Intel)



      reply	other threads:[~2021-06-21 22:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-15 20:14 [Intel-wired-lan] [PATCH net] ice: do not abort devlink info if PBA can't be found Jacob Keller
2021-06-21 22:12 ` Brelinski, TonyX [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=SJ0PR11MB5662931B7D5F0E3C1A628D4AFA0A9@SJ0PR11MB5662.namprd11.prod.outlook.com \
    --to=tonyx.brelinski@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.