From: Jiri Pirko <jiri@resnulli.us>
To: Vasundhara Volam <vasundhara-v.volam@broadcom.com>
Cc: davem@davemloft.net, netdev@vger.kernel.org,
Jakub Kicinski <kuba@kernel.org>, Jiri Pirko <jiri@mellanox.com>,
Jacob Keller <jacob.e.keller@intel.com>,
Michael Chan <michael.chan@broadcom.com>
Subject: Re: [PATCH v2 net-next 1/7] devlink: Add macro for "fw.api" to info_get cb.
Date: Thu, 26 Mar 2020 10:28:50 +0100 [thread overview]
Message-ID: <20200326092850.GS11304@nanopsycho.orion> (raw)
In-Reply-To: <1585204021-10317-2-git-send-email-vasundhara-v.volam@broadcom.com>
Thu, Mar 26, 2020 at 07:26:58AM CET, vasundhara-v.volam@broadcom.com wrote:
>Add definition and documentation for the new generic info "fw.api".
>"fw.api" specifies the version of the software interfaces between
>driver and overall firmware.
>
>Cc: Jakub Kicinski <kuba@kernel.org>
>Cc: Jiri Pirko <jiri@mellanox.com>
>Cc: Jacob Keller <jacob.e.keller@intel.com>
>Signed-off-by: Vasundhara Volam <vasundhara-v.volam@broadcom.com>
>Signed-off-by: Michael Chan <michael.chan@broadcom.com>
Looks sane to me.
Reviewed-by: Jiri Pirko <jiri@mellanox.com>
next prev parent reply other threads:[~2020-03-26 9:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-26 6:26 [PATCH v2 net-next 0/7] bnxt_en: Updates to devlink info_get cb Vasundhara Volam
2020-03-26 6:26 ` [PATCH v2 net-next 1/7] devlink: Add macro for "fw.api" to " Vasundhara Volam
2020-03-26 9:28 ` Jiri Pirko [this message]
2020-03-26 6:26 ` [PATCH v2 net-next 2/7] bnxt_en: Add fw.api version to devlink " Vasundhara Volam
2020-03-26 6:27 ` [PATCH v2 net-next 3/7] devlink: Add macro for "hw.addr" to " Vasundhara Volam
2020-03-26 9:26 ` Jiri Pirko
2020-03-26 11:02 ` Vasundhara Volam
2020-03-26 15:54 ` Jiri Pirko
2020-03-26 16:03 ` Vasundhara Volam
2020-03-26 6:27 ` [PATCH v2 net-next 4/7] bnxt_en: Add hw addr to 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=20200326092850.GS11304@nanopsycho.orion \
--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).