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

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

Message-ID: <20211117084854.0d44d64b@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com>
Date:   Wed, 17 Nov 2021 08:48:54 -0800
From:   Jakub Kicinski <kuba@...nel.org>
To:     Jamal Hadi Salim <jhs@...atatu.com>
Cc:     Davide Caratti <dcaratti@...hat.com>,
        Li Zhijian <zhijianx.li@...el.com>, shuah@...nel.org,
        linux-kselftest@...r.kernel.org, lizhijian@...fujitsu.com,
        linux-kernel@...r.kernel.org, lkp@...el.com, philip.li@...el.com
Subject: Re: [PATCH v2 1/3] selftests/tc-testing: add exit code

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.