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: <73263547-f3a2-4156-bca9-45b647e67830@nvidia.com>
Date: Fri, 7 Mar 2025 00:32:34 +0200
From: Gal Pressman <gal@...dia.com>
To: Jakub Kicinski <kuba@...nel.org>, Tariq Toukan <ttoukan.linux@...il.com>
Cc: 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
Subject: Re: [PATCH net] net/mlx5: Fill out devlink dev info only for PFs

On 06/03/2025 23: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.

Do you not agree?

> 
> 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.

Is this new rule mlx5 specific? How come the driver maintainers are not
aware of it?

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ