[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230403152053.53253d7e@kernel.org>
Date: Mon, 3 Apr 2023 15:20:53 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: Shannon Nelson <shannon.nelson@....com>
Cc: Pavan Kumar Linga <pavan.kumar.linga@...el.com>,
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, Alan Brady <alan.brady@...el.com>,
Madhu Chittim <madhu.chittim@...el.com>,
Phani Burra <phani.r.burra@...el.com>
Subject: Re: [Intel-wired-lan] [PATCH net-next 01/15] virtchnl: add virtchnl
version 2 ops
On Mon, 3 Apr 2023 15:01:55 -0700 Shannon Nelson wrote:
> > diff --git a/drivers/net/ethernet/intel/idpf/virtchnl2.h b/drivers/net/ethernet/intel/idpf/virtchnl2.h
>
> If this is to be a standardized interface, why is this header buried in
> the driver specific directory instead of something more accessible like
> include/linux/idpf?
The noise about this driver being "a standard" is quite confusing.
Are you considering implementing any of it?
I haven't heard of anyone who is yet, so I thought all this talk of
a standard is pretty empty from the technical perspective :(
Powered by blists - more mailing lists