lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <52826c35-eba1-40fb-bfa9-23a87400bfa4@lunn.ch>
Date: Fri, 19 May 2023 20:22:46 +0200
From: Andrew Lunn <andrew@...n.ch>
To: "Samudrala, Sridhar" <sridhar.samudrala@...el.com>
Cc: "Michael S. Tsirkin" <mst@...hat.com>,
	Emil Tantilov <emil.s.tantilov@...el.com>,
	intel-wired-lan@...ts.osuosl.org, shannon.nelson@....com,
	simon.horman@...igine.com, leon@...nel.org, decot@...gle.com,
	willemb@...gle.com, jesse.brandeburg@...el.com,
	anthony.l.nguyen@...el.com, davem@...emloft.net,
	edumazet@...gle.com, kuba@...nel.org, pabeni@...hat.com,
	netdev@...r.kernel.org,
	"Singhai, Anjali" <anjali.singhai@...el.com>,
	"Orr, Michael" <michael.orr@...el.com>
Subject: Re: [PATCH iwl-next v4 00/15] Introduce Intel IDPF driver

> +config IDPF
> +	tristate "Intel(R) Infrastructure Data Path Function Support"
> +	depends on PCI_MSI
> +	select DIMLIB
> +	help
> +	  This driver supports Intel(R) Infrastructure Processing Unit (IPU)
> +	  devices.
> 
> It can be updated with Intel references removed when the spec becomes
> standard and meets the community requirements.

Is IPU Intels name for the hardware which implements DPF? I assume
when 'Intel' is dropped, IPU would also be dropped? Which leaves the
help empty.

And i assume when it is no longer tied to Intel, the Kconfig entry
will move somewhere else, because at the moment, it appears to appear
under Intel, when it probably should be at a higher level, maybe
'Network device support'? And will the code maybe move to net/idpf?

<tongue in cheek>
Maybe put it into driver/staging/idpf for the moment?
</tongue in cheek>

	 Andrew

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ