netdev - Re: Pending taprio fixes

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <87a5f2cnbi.fsf@intel.com>
Date: Thu, 17 Oct 2024 16:38:25 -0700
From: Vinicius Costa Gomes <vinicius.gomes@...el.com>
To: Dmitry Antipov <dmantipov@...dex.ru>, Jakub Kicinski <kuba@...nel.org>,
 Paolo Abeni <pabeni@...hat.com>
Cc: netdev@...r.kernel.org, lvc-project@...uxtesting.org
Subject: Re: Pending taprio fixes

Hi,

Dmitry Antipov <dmantipov@...dex.ru> writes:

> Just one more friendly reminder.
>

Taking a look at:

https://patchwork.kernel.org/project/netdevbpf/list/?series=900198

A couple of process related things jump up:

  1. The subject prefix was not set in the "cover letter", so perhaps
  people/tools didn't see them as patches that should be considered,
  also the lack of "net" in the subject prefix, made patchwork to guess
  wrong, that this is targetting net-next;

  2. You missed people from one of the patches CC list, running
  get_maintainer.pl on the patches helps here;

  3. You didn't add my "Acked-by" to this version;

Most probably, a mix of (1) and (2) was the reason that no one else
reacted to v5. I should have been more clear about those.

Cheers,
-- 
Vinicius