netdev - Re: [PATCH v2 1/3] selftests/tc-testing: add exit code

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

Message-ID: <236a81d3-db14-902f-8833-377ec0a9b7da@intel.com>
Date:   Fri, 3 Dec 2021 10:21:31 +0800
From:   Li Zhijian <zhijianx.li@...el.com>
To:     Jamal Hadi Salim <jhs@...atatu.com>,
        Jakub Kicinski <kuba@...nel.org>
Cc:     Davide Caratti <dcaratti@...hat.com>, shuah@...nel.org,
        linux-kselftest@...r.kernel.org, lizhijian@...fujitsu.com,
        linux-kernel@...r.kernel.org, lkp@...el.com, philip.li@...el.com,
        Networking <netdev@...r.kernel.org>
Subject: Re: [PATCH v2 1/3] selftests/tc-testing: add exit code

CCed netdev

Kindly ping


On 18/11/2021 00:51, Jamal Hadi Salim wrote:
> On 2021-11-17 11:48, Jakub Kicinski wrote:
>> On Wed, 17 Nov 2021 11:41:18 -0500 Jamal Hadi Salim wrote:
>>> Did you mean adding a maintainer for tdc or just generally point
>>> who/what to involve when making changes? Typically the mailing list
>>> should be sufficient. Outside the list, at the moment, any outstanding
>>> issues on tdc are discussed/resolved in the monthly TC meetups (where
>>> all the stake holders show up)...
>>
>> I'm mostly interested in the code review and merging part.
>>
>> Would be great to have a MAINTAINERS entry with a set of folks
>> who can review patches, so that get_maintainers.pl can do its job.
>>
>> At the very least to make sure netdev is CCed.
>
> ACK.
>
> cheers,
> jamal
>