[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZCV6fZfuX5O8sRtA@nvidia.com>
Date: Thu, 30 Mar 2023 09:03:09 -0300
From: Jason Gunthorpe <jgg@...dia.com>
To: Pavan Kumar Linga <pavan.kumar.linga@...el.com>
Cc: intel-wired-lan@...ts.osuosl.org, netdev@...r.kernel.org,
shiraz.saleem@...el.com, emil.s.tantilov@...el.com,
willemb@...gle.com, decot@...gle.com, joshua.a.hay@...el.com,
sridhar.samudrala@...el.com
Subject: Re: [Intel-wired-lan] [PATCH net-next 00/15] Introduce IDPF driver
On Wed, Mar 29, 2023 at 07:03:49AM -0700, Pavan Kumar Linga wrote:
> This patch series introduces the Infrastructure Data Path Function (IDPF)
> driver. It is used for both physical and virtual functions. Except for
> some of the device operations the rest of the functionality is the same
> for both PF and VF. IDPF uses virtchnl version2 opcodes and structures
> defined in the virtchnl2 header file which helps the driver to learn
> the capabilities and register offsets from the device Control Plane (CP)
> instead of assuming the default values.
Isn't IDPF currently being "standardized" at OASIS?
Has a standard been ratified? Isn't it rather premature to merge a
driver for a standard that doesn't exist?
Publicly posting pre-ratification work is often against the IP
policies of standards orgs, are you even legally OK to post this?
Confused,
Jason
Powered by blists - more mailing lists