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: <1d20d912-3c9a-4718-b4c9-6f5e83d2da70@redhat.com>
Date: Tue, 4 Feb 2025 16:48:05 +0100
From: Paolo Abeni <pabeni@...hat.com>
To: Jakub Kicinski <kuba@...nel.org>
Cc: davem@...emloft.net, netdev@...r.kernel.org, edumazet@...gle.com,
 andrew+netdev@...n.ch, horms@...nel.org
Subject: Re: [PATCH net 2/2] MAINTAINERS: add a sample ethtool section entry

On 2/4/25 4:37 PM, Jakub Kicinski wrote:
> On Tue, 4 Feb 2025 10:26:40 +0100 Paolo Abeni wrote:
>> What about tying the creation of the entry to some specific contribution?
> 
> Sure. I'm adding this so that we have a commit to point people at 
> as an example when they contribute what should be a new section.
> Maybe I don't understand the question..

I meant that this section could be added together with a new associated
name when a suitable person will pop-up.

Or course that would not help as an example, and I initially did see
there was such a goal. I'm fine with adding new entry even now.

/P


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ