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: <7bb21136-83e8-4eff-b8f7-dc4af70c2199@gmail.com>
Date: Thu, 6 Mar 2025 21:20:58 +0200
From: Tariq Toukan <ttoukan.linux@...il.com>
To: Jakub Kicinski <kuba@...nel.org>
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, Gal Pressman <gal@...dia.com>
Subject: Re: [PATCH net] net/mlx5: Fill out devlink dev info only for PFs

On 06/03/2025 4:30, Jakub Kicinski wrote:
> On Wed, 5 Mar 2025 20:55:15 +0200 Tariq Toukan wrote:
>> Reviewed-by: Tariq Toukan <tariqt@...dia.com>
> 
> Too late, take it via your tree, please.
> You need to respond within 24h or take the patches.

Never heard of a 24h rule. Not clear to me what rule you're talking 
about, what's the rationale behind it, and where it's coming from.

It's pretty obvious for everyone that responding within 24h cannot be 
committed, and is not always achievable.

Moreover, this contradicts with maintainer-netdev.rst, which explicitly 
aligns the expected review timeline to be 48h for triage, also to give 
the opportunity for more reviewers to share their thoughts.

Tariq.