[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20200324.164906.998922318294541493.davem@davemloft.net>
Date: Tue, 24 Mar 2020 16:49:06 -0700 (PDT)
From: David Miller <davem@...emloft.net>
To: kuba@...nel.org
Cc: netdev@...r.kernel.org, kernel-team@...com, eugenem@...com,
jacob.e.keller@...el.com, jiri@...nulli.us,
michael.chan@...adcom.com, snelson@...sando.io,
jesse.brandeburg@...el.com, rdunlap@...radead.org,
vasundhara-v.volam@...adcom.com
Subject: Re: [PATCH net-next v3] devlink: expand the devlink-info
documentation
From: Jakub Kicinski <kuba@...nel.org>
Date: Tue, 24 Mar 2020 10:30:16 -0700
> We are having multiple review cycles with all vendors trying
> to implement devlink-info. Let's expand the documentation with
> more information about what's implemented and motivation behind
> this interface in an attempt to make the implementations easier.
>
> Describe what each info section is supposed to contain, and make
> some references to other HW interfaces (PCI caps).
>
> Document how firmware management is expected to look, to make
> it clear how devlink-info and devlink-flash work in concert.
>
> Name some future work.
>
> v2: - improve wording
> v3: - improve wording
>
> Signed-off-by: Jakub Kicinski <kuba@...nel.org>
> Reviewed-by: Randy Dunlap <rdunlap@...radead.org>
Applied, thanks.
Powered by blists - more mailing lists