[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <d0c32c34-b0a4-ce1e-35d6-1894222e825a@mojatatu.com>
Date: Wed, 17 Nov 2021 11:51:36 -0500
From: Jamal Hadi Salim <jhs@...atatu.com>
To: Jakub Kicinski <kuba@...nel.org>
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 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
Powered by blists - more mailing lists