[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200326134025.2c2c94f8@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com>
Date: Thu, 26 Mar 2020 13:40:25 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: Vasundhara Volam <vasundhara-v.volam@...adcom.com>
Cc: davem@...emloft.net, netdev@...r.kernel.org,
Jacob Keller <jacob.e.keller@...el.com>,
Michael Chan <michael.chan@...adcom.com>
Subject: Re: [PATCH v3 net-next 1/5] devlink: Add macro for "fw.api" to
info_get cb.
On Thu, 26 Mar 2020 17:32:34 +0530 Vasundhara Volam 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@...nel.org>
> Cc: Jacob Keller <jacob.e.keller@...el.com>
> Reviewed-by: Jiri Pirko <jiri@...lanox.com>
> Signed-off-by: Vasundhara Volam <vasundhara-v.volam@...adcom.com>
> Signed-off-by: Michael Chan <michael.chan@...adcom.com>
> ---
> v1->v2: Rename macro to "fw.api" from "drv.spec".
I suggested "fw.mgmt.api", like Intel has. What else those this API
number covers beyond management? Do you negotiated descriptor formats
for the datapath?
Powered by blists - more mailing lists