Re: [PATCH 8/9] docs: maintainers_include: don't ignore invalid profile entries

[Mauro Carvalho Chehab]

On Tue, 05 May 2026 12:16:03 +0100
"Gary Guo" <gary@xxxxxxxxxxx> wrote:

> On Tue May 5, 2026 at 6:45 AM BST, Mauro Carvalho Chehab wrote:
> > On Tue, 5 May 2026 02:20:45 +0200
> > Miguel Ojeda <miguel.ojeda.sandonis@xxxxxxxxx> wrote:
> >  
> >> On Tue, May 5, 2026 at 2:08 AM Mauro Carvalho Chehab
> >> <mchehab+huawei@xxxxxxxxxx> wrote:  
> >> >
> >> > Also, with time, maintainers may change their employers while still
> >> > keeping their maintainership status.
> >> >
> >> > So, I'd say that whatever is there at the "P" entry, or where it is
> >> > located (either on a ReST file at the Kernel or on some external URL),
> >> > it should reflect the model that a maintainer or subsystem community
> >> > that actively participate at the Kernel development agrees with.
> >> > This should be vendor-agnostic.    
> >> 
> >> I am not sure what you mean. By "vendored" I don't mean
> >> companies/employers, I mean that the file comes from an upstream
> >> repository:
> >> 
> >>   https://github.com/Rust-for-Linux/pin-init/blob/main/CONTRIBUTING.md
> >> 
> >> Nevertheless, it is true that this really is a special case, in that
> >> the upstream project decided to provide something that could then be
> >> fit into the `P:` field.
> >> 
> >> One could say "let's ask them to do rst upstream", but to be honest,
> >> it is simpler to just put a hyperlink to GitHub's rendered file.
> >> Markdown is anyway a better fit for their file.  
> >
> > Ok. Then it P entry could be:
> >
> > 	P: https://github.com/Rust-for-Linux/pin-init/blob/main/CONTRIBUTING.md  
> 
> If you send a patch I can queue it up for 7.2. Or would you want this to be
> taken via docs tree instead?

It doesn't matter much but placing it at the documentation series
will keep this change together with the other patches, so I guess
it would be a little better.

I'll be sending the new patch series soon with this change there
as well.

-- 
Thanks,
Mauro