Re: [PATCH net-next v20 14/14] mm: page_frag: add an entry in MAINTAINERS for page_frag

[Yunsheng Lin]

On 2024/10/10 0:32, Paolo Abeni wrote:
> Hi,

Hi,

> 
> On 10/9/24 06:01, Yunsheng Lin wrote:
>> On 2024/10/9 8:43, Jakub Kicinski wrote:
>>> On Tue, 8 Oct 2024 19:20:48 +0800 Yunsheng Lin wrote:
>>>> +M:    Yunsheng Lin <linyunsheng@xxxxxxxxxx>
>>>
>>> The bar for maintaining core code is very high, if you'd
>>> like to be a maintainer please start small.
>>
>> I did start small with the page_pool case, as mentioned in
>> [1] of a similar comment, and the page_frag is a small
>> subsystem/library as mentioned in commit log.
>>
>> I think I still might need a second opinion here.
>>
>> 1. https://lore.kernel.org/linux-kernel/dea82ac3-65fc-c941-685f-9d4655aa4a52@xxxxxxxxxx/
> 
> Please note that the 'small' part here does not refer strictly to code size. Any core networking code has the bar significantly higher than i.e. NIC drivers - even if the latter could count order of magnitude more LoC.
> AFAICS there is an unwritten convention that people are called to maintain core code, as opposed to people appointing themself to maintain driver code.

Is there any discussion that is referring to above 'unwritten convention'?
As my pool community experience tells me the above 'unwritten
convention' is mainly referring to well-established subsystem that is
already in the MAINTAINERS, and page_frag is not really a subsystem or
library before this patchset, it seems common to me that someone being
willing and able to turn it into a subsystem or library might become the
co-maintainer if she/he is also willing to co-maintain it.

> 
> Cheers,
> 
> Paolo
> 
>