public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: vasundhara-v.volam@broadcom.com
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH v4 net-next 0/6] bnxt_en: Updates to devlink info_get cb
Date: Fri, 27 Mar 2020 15:35:03 -0700 (PDT)	[thread overview]
Message-ID: <20200327.153503.880515420927730742.davem@davemloft.net> (raw)
In-Reply-To: <1585301692-25954-1-git-send-email-vasundhara-v.volam@broadcom.com>

From: Vasundhara Volam <vasundhara-v.volam@broadcom.com>
Date: Fri, 27 Mar 2020 15:04:50 +0530

> This series adds support for a generic macro to devlink info_get cb.
> Adds support for fw.mgmt.api and board.id info to bnxt_en driver info_get
> cb. Also, updates the devlink-info.rst and bnxt.rst documentation
> accordingly.
> 
> This series adds a patch to fix few macro names that maps to bnxt_en
> firmware versions.
> 
> ---
> v1->v2: Remove ECN dev param, base_mh_addr and serial number info support
> in this series.
> Rename drv.spec macro to fw.api.
> ---
> v2->v3: Remove hw.addr info as it is per netdev but not per device info.
> ---
> v3->v4: Rename "fw.api" to "fw.mgmt.api".
> Also, add a patch that modifies few macro names in info_get command,
> to match the devlink documentation.

Series applied, thank you.

      parent reply	other threads:[~2020-03-27 22:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-27  9:34 [PATCH v4 net-next 0/6] bnxt_en: Updates to devlink info_get cb Vasundhara Volam
2020-03-27  9:34 ` [PATCH v4 net-next 1/6] devlink: Add macro for "fw.mgmt.api" to " Vasundhara Volam
2020-03-27  9:44   ` Jiri Pirko
2020-03-27  9:34 ` [PATCH v4 net-next 2/6] bnxt_en: Add fw.mgmt.api version to devlink " Vasundhara Volam
2020-03-27 17:39 ` [PATCH v4 net-next 0/6] bnxt_en: Updates " Jakub Kicinski
2020-03-27 22:35 ` David Miller [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=20200327.153503.880515420927730742.davem@davemloft.net \
    --to=davem@davemloft.net \
    --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