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: <ahh3ctzo2gs5zwwhzq33oudr4hmplznewczbfil74zddfabx4n@t7lwrx6eh4ym>
Date: Fri, 7 Mar 2025 13:35:28 +0100
From: Jiri Pirko <jiri@...nulli.us>
To: Jakub Kicinski <kuba@...nel.org>
Cc: Tariq Toukan <ttoukan.linux@...il.com>, netdev@...r.kernel.org, 
	davem@...emloft.net, edumazet@...gle.com, pabeni@...hat.com, saeedm@...dia.com, 
	leon@...nel.org, tariqt@...dia.com, andrew+netdev@...n.ch, 
	Gal Pressman <gal@...dia.com>
Subject: Re: [PATCH net] net/mlx5: Fill out devlink dev info only for PFs

Thu, Mar 06, 2025 at 08:43:55PM +0100, kuba@...nel.org wrote:

[...]


>nvidia's employees patches should go via your tree, in the first place.

Why? I've been in Mellanox/Nvidia for almost 10 years and this is
actually the first time I hit this. I'm used to send patches directly,
I've been doing that for almost 15+ years and this was never issue.
Where this rule is written down? What changed?

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ