netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jiri Pirko <jiri@resnulli.us>
To: Vasundhara Volam <vasundhara-v.volam@broadcom.com>
Cc: davem@davemloft.net, netdev@vger.kernel.org,
	michael.chan@broadcom.com, kuba@kernel.org, jiri@mellanox.com,
	jacob.e.keller@intel.com
Subject: Re: [PATCH net-next 0/2] devlink: Add board_serial_number field to info_get cb.
Date: Sat, 20 Jun 2020 14:09:49 +0200	[thread overview]
Message-ID: <20200620120949.GA2748@nanopsycho> (raw)
In-Reply-To: <1592640947-10421-1-git-send-email-vasundhara-v.volam@broadcom.com>

Sat, Jun 20, 2020 at 10:15:45AM CEST, vasundhara-v.volam@broadcom.com wrote:
>This patchset adds support for board_serial_number to devlink info_get
>cb and also use it in bnxt_en driver.
>
>Sample output:
>
>$ devlink dev info pci/0000:af:00.1
>pci/0000:af:00.1:
>  driver bnxt_en
>  serial_number 00-10-18-FF-FE-AD-1A-00
>  board_serial_number 433551F+172300000
>  versions:
>      fixed:
>        board.id 7339763 Rev 0.

We have board.id already here. I understand that the serial number does
not belong under the same nest, as it is not a "version".

However, could you at least maintain the format:
board.serial_number
?


>        asic.id 16D7
>        asic.rev 1
>      running:
>        fw 216.1.216.0
>        fw.psid 0.0.0
>        fw.mgmt 216.1.192.0
>        fw.mgmt.api 1.10.1
>        fw.ncsi 0.0.0.0
>        fw.roce 216.1.16.0
>
>Vasundhara Volam (2):
>  devlink: Add support for board_serial_number to info_get cb.
>  bnxt_en: Add board_serial_number field to info_get cb
>
> Documentation/networking/devlink/devlink-info.rst | 12 +++++-------
> drivers/net/ethernet/broadcom/bnxt/bnxt_devlink.c |  7 +++++++
> include/net/devlink.h                             |  2 ++
> include/uapi/linux/devlink.h                      |  2 ++
> net/core/devlink.c                                |  8 ++++++++
> 5 files changed, 24 insertions(+), 7 deletions(-)
>
>-- 
>1.8.3.1
>

  parent reply	other threads:[~2020-06-20 12:09 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-20  8:15 [PATCH net-next 0/2] devlink: Add board_serial_number field to info_get cb Vasundhara Volam
2020-06-20  8:15 ` [PATCH net-next 1/2] devlink: Add support for board_serial_number " Vasundhara Volam
2020-06-20 13:06   ` Jiri Pirko
2020-06-20  8:15 ` [PATCH net-next 2/2] bnxt_en: Add board_serial_number field " Vasundhara Volam
2020-06-20 13:07   ` Jiri Pirko
2020-06-20 16:19     ` Vasundhara Volam
2020-06-20 12:09 ` Jiri Pirko [this message]
2020-06-20 16:17   ` [PATCH net-next 0/2] devlink: " Vasundhara Volam

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=20200620120949.GA2748@nanopsycho \
    --to=jiri@resnulli.us \
    --cc=davem@davemloft.net \
    --cc=jacob.e.keller@intel.com \
    --cc=jiri@mellanox.com \
    --cc=kuba@kernel.org \
    --cc=michael.chan@broadcom.com \
    --cc=netdev@vger.kernel.org \
    --cc=vasundhara-v.volam@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).