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: <6cxx4i4t66q6hm2df46lirt3qkd4v2ryuoytuqmxqe6glgfsu5@3nvtleuvy5qr>
Date: Mon, 10 Mar 2025 13:16:57 +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

Fri, Mar 07, 2025 at 05:20:53PM +0100, kuba@...nel.org wrote:
>On Fri, 7 Mar 2025 13:35:28 +0100 Jiri Pirko 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.
>
>You probably mostly change the driver together with core, like devlink.
>In those cases you can post outside the main stream.

Okay, that is mostly what I do, correct.


>
>> Where this rule is written down? What changed?
>
>It was always like this, since before I became a maintainer.
>I think what happened is Saeed handed the maintainership over
>without "writing down" all the rules that we established over
>the years.
>
>Obviously he will now probably disagree with me. Because y'all
>apparently have no time to review patches, but playing victim
>you have all the time in the world for.
>
>There are only two vendors big enough to warrant a special process
>(Intel and nVidia), and we make reasonable accommodations (like
>the one above) so it's impractical to write all the rules down.
>
>Not to mention the fact that you should perhaps, in an ideal 
>world, just try to be a good community member, instead acting
>as if we're signing a business contract.

I'm always trying to be a good community member. I just can't behave in
cases I have no clue how, that's all. :)


>
>Have a nice weekend.