[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Yv4geqG6r3OVDNvB@corigine.com>
Date: Thu, 18 Aug 2022 13:20:26 +0200
From: Simon Horman <simon.horman@...igine.com>
To: ecree@...inx.com
Cc: netdev@...r.kernel.org, linux-net-drivers@....com,
davem@...emloft.net, kuba@...nel.org, pabeni@...hat.com,
edumazet@...gle.com, corbet@....net, linux-doc@...r.kernel.org,
jacob.e.keller@...el.com, jesse.brandeburg@...el.com,
michael.chan@...adcom.com, andy@...yhouse.net, saeed@...nel.org,
jiri@...nulli.us, snelson@...sando.io, alexander.duyck@...il.com,
rdunlap@...radead.org, Edward Cree <ecree.xilinx@...il.com>
Subject: Re: [RFC PATCH v2 net-next] docs: net: add an explanation of VF (and
other) Representors
On Mon, Aug 15, 2022 at 03:22:51PM +0100, ecree@...inx.com wrote:
> From: Edward Cree <ecree.xilinx@...il.com>
>
> There's no clear explanation of what VF Representors are for, their
> semantics, etc., outside of vendor docs and random conference slides.
> Add a document explaining Representors and defining what drivers that
> implement them are expected to do.
>
> Signed-off-by: Edward Cree <ecree.xilinx@...il.com>
Thanks a lot for working on this, it looks very nice to me.
Reviewed-by: Simon Horman <simon.horman@...igine.com>
Powered by blists - more mailing lists