Pierrick Bouvier <[email protected]> writes:
> On 5/20/2026 7:52 AM, Markus Armbruster wrote:
>> Philippe Mathieu-Daudé <[email protected]> writes:
>>
>>> Fixes: 812b31d3f91 ("configs: rename default-configs to configs and
>>> reorganise")
>>> Signed-off-by: Philippe Mathieu-Daudé <[email protected]>
>>> ---
>>> MAINTAINERS | 2 +-
>>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>>
>>> diff --git a/MAINTAINERS b/MAINTAINERS
>>> index b75f3222f2f..2a4d124fb3c 100644
>>> --- a/MAINTAINERS
>>> +++ b/MAINTAINERS
>>> @@ -256,7 +256,7 @@ X: target/hexagon/gen_idef_parser_funcs.py
>>> F: linux-user/hexagon/
>>> F: tests/tcg/hexagon/
>>> F: disas/hexagon.c
>>> -F: configs/targets/hexagon-linux-user/default.mak
>>> +F: configs/targets/hexagon-linux-user.mak
>>> F: docker/dockerfiles/debian-hexagon-cross.docker
>>
>> This one's wrong, too.
>>
>> I have an unsent patch fixing both. In fact, I have an unsent series
>> fixing *all* F: patterns that don't resolve to any file.
>>
>
> I planned to take a look at this, and would be happy to review yours.
I hope to post tomorrow. Review is always appreciated!
> Any chance you have a script that we could integrate directly into our
> meson.build? (I feel it's better than checkpatch, since checkpatch is
> not blocking anything CI wise).
Good idea.
Here's my quick & dirty way to find broke F:
$ ls `sed -n 's/^F: *//p' MAINTAINERS ` >/dev/null
Easily fooled by untracked files. I double-checked in a fresh clone
just to be sure.
> This way, any time a project is configured (not built, configured), it
> would trigger a check. Since every file removal/adding implies a
> meson.build modification, it should keep the MAINTAINERS file consistent
> by design.
Yep.
>>> F: gdbstub/gdb-xml/hexagon*.xml
>>> T: git https://github.com/quic/qemu.git hex-next
