netdev - Re: [PATCH net] net/mlx5: Fill out devlink dev info only for PFs

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] [day] [month] [year] [list]

Message-ID: <20250309075029.GA10087@unreal>
Date: Sun, 9 Mar 2025 09:50:29 +0200
From: Leon Romanovsky <leon@...nel.org>
To: Jiri Pirko <jiri@...nulli.us>
Cc: Jakub Kicinski <kuba@...nel.org>,
	Tariq Toukan <ttoukan.linux@...il.com>, netdev@...r.kernel.org,
	davem@...emloft.net, edumazet@...gle.com, pabeni@...hat.com,
	saeedm@...dia.com, 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

On Fri, Mar 07, 2025 at 01:35:28PM +0100, Jiri Pirko wrote:
> 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?

Maintainer?

I'm second to your feelings.

Long standing contributors sent patches mostly directly. It was definitely
encouraged to send long series through Saeed, but simple, one line fixes were
accepted without extra hop.

It was easy and convenient for everyone.

Thanks