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

Message-ID: <Z8ohE4FuLBUf6NvX@x130>
Date: Thu, 6 Mar 2025 14:26:27 -0800
From: Saeed Mahameed <saeed@...nel.org>
To: Jakub Kicinski <kuba@...nel.org>
Cc: Tariq Toukan <ttoukan.linux@...il.com>, Jiri Pirko <jiri@...nulli.us>,
	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

On 06 Mar 13:46, Jakub Kicinski wrote:
>On Thu, 6 Mar 2025 23:13:33 +0200 Tariq Toukan wrote:
>> >> So no less than two working days for any subsystem.
>> >> Okay, now this makes more sense.
>> >
>> > Could you explain to me why this is a problem for you?
>>
>> Nothing special about "me" here.
>>
>> I thought it's obvious. As patches are coming asynchronously, it is not
>> rare to won't be able to respond within a single working day.
>>
>> This becomes significantly rarer with two consecutive working days.
>
>On one thread Saeed is claiming that nVidia is a major netdev
>contributor, and pillar of the community.
>
>On another thread it's too hard for the main mlx5 maintainer
>to open their inbox once a day to look at patches for their
>own driver, that they were CCed on.
>

People have personal circumstances and constraints it has nothing to do
with the employer or the fact that they are a maintainer or a major
contributor.
24hr is a bit too tight for some people which is understandable,
48hr response time works well for everyone.