Re: [PATCH] MAINTAINERS: Fix hexagon-linux-user.mak path
Pierrick Bouvier writes:
> On 5/20/2026 7:52 AM, Markus Armbruster wrote:
>> Philippe Mathieu-Daudé writes:
>>
>>> Fixes: 812b31d3f91 ("configs: rename default-configs to configs and
>>> reorganise")
>>> Signed-off-by: Philippe Mathieu-Daudé
>>> ---
>>> 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
Re: [PATCH] MAINTAINERS: Fix hexagon-linux-user.mak path
On 5/20/2026 7:52 AM, Markus Armbruster wrote:
> Philippe Mathieu-Daudé writes:
>
>> Fixes: 812b31d3f91 ("configs: rename default-configs to configs and
>> reorganise")
>> Signed-off-by: Philippe Mathieu-Daudé
>> ---
>> 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.
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).
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.
>> F: gdbstub/gdb-xml/hexagon*.xml
>> T: git https://github.com/quic/qemu.git hex-next
>
Re: [PATCH] MAINTAINERS: Fix hexagon-linux-user.mak path
On 5/20/2026 9:05 AM, Philippe Mathieu-Daudé wrote:
> On 20/5/26 15:09, Markus Armbruster wrote:
>> Philippe Mathieu-Daudé writes:
>>
>>> On 20/5/26 14:57, Philippe Mathieu-Daudé wrote:
On 20/5/26 14:52, Markus Armbruster wrote:
> Philippe Mathieu-Daudé writes:
>
>> Fixes: 812b31d3f91 ("configs: rename default-configs to configs
>> and reorganise")
>> Signed-off-by: Philippe Mathieu-Daudé
>> ---
>> 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.
Already fixed in Alex's tree:
https://lore.kernel.org/qemu-devel/2026051810.80735-2-
[email protected]/
Pierrick suggested to repost patch dependencies already queued in
maintainer tree when posting series; while this seem counter
productive it could indeed have saved us time.
> 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 looked for your series without success, then realized you mentioned
>>> it is "unsent". This patch is still valid then.
>>
>> Yes.
>>
>>> Why mention unsent
>>> work?
>>
>> To avoid duplicated work.
>
> I'm not sure this thread is making sense o_O
>
> Let's try to figure what you meant here. I'm not racing to get
> this patch in nor enjoying duplicating work, but this is the
> mailing list rules (due to the intrinsic email workflow latency,
> not to mention subscriber processing their INBOX in FIFO mode).
>
> See for example last week at least 3 developers fixed the same
> GCC warning issue. Generically, how could we improve that?
>
Ideally, by merging such fixes faster (in one hour, not N days).
More realistically, having a daily CI job that tests latest (stable)
version of compilers before they hit stable distros. This way, all build
issues/warnings would never impact anyone.
For some bugs, some duplication is inevitable, but it should 99% of
those easy build fixes.
For the rest, sending "unsent" work seems like an easy fix :).
Regards,
Pierrick
Re: [PATCH] MAINTAINERS: Fix hexagon-linux-user.mak path
Philippe Mathieu-Daudé writes:
> On 20/5/26 15:09, Markus Armbruster wrote:
>> Philippe Mathieu-Daudé writes:
>>
>>> On 20/5/26 14:57, Philippe Mathieu-Daudé wrote:
On 20/5/26 14:52, Markus Armbruster wrote:
> Philippe Mathieu-Daudé writes:
>
>> Fixes: 812b31d3f91 ("configs: rename default-configs to configs and
>> reorganise")
>> Signed-off-by: Philippe Mathieu-Daudé
>> ---
>> 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.
Already fixed in Alex's tree:
https://lore.kernel.org/qemu-devel/[email protected]/
Pierrick suggested to repost patch dependencies already queued in
maintainer tree when posting series; while this seem counter
productive it could indeed have saved us time.
> 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 looked for your series without success, then realized you mentioned
>>> it is "unsent". This patch is still valid then.
>>
>> Yes.
>>
>>> Why mention unsent work?
>> To avoid duplicated work.
>
> I'm not sure this thread is making sense o_O
Are we talking past each other?
> Let's try to figure what you meant here. I'm not racing to get
> this patch in nor enjoying duplicating work, but this is the
> mailing list rules (due to the intrinsic email workflow latency,
> not to mention subscriber processing their INBOX in FIFO mode).
Let me recap the obvious :)
1. First workable patch on the list has priority, with a generous
interpretation of "workable".
2. If a workable patch on the list overlaps with one I haven't sent, I
rebase mine onto it. No arguing, no whining.
In fact, I did exactly that, and then told you: "I've been picking [your
patches] into my tree". When my patches are ready, I intend to post
them with a bunch of Based-on: pointing to yours, or include yours with
mine, whatever feels more convenient.
Okay?
> See for example last week at least 3 developers fixed the same
> GCC warning issue. Generically, how could we improve that?
I don't have better ideas than "watch the mailing list", and "let the
right people know what you're doing".
Oh :( I already sent various patches about that yesterday :(
>>
>> I've been picking them into my tree as I went. I may have missed the
>> odd patch, but I'll fix that.
>>
>
>> F: gdbstub/gdb-xml/hexagon*.xml
>> T: git https://github.com/quic/qemu.git hex-next
>>
Re: [PATCH] MAINTAINERS: Fix hexagon-linux-user.mak path
On 20/5/26 15:09, Markus Armbruster wrote:
Philippe Mathieu-Daudé writes:
On 20/5/26 14:57, Philippe Mathieu-Daudé wrote:
On 20/5/26 14:52, Markus Armbruster wrote:
Philippe Mathieu-Daudé writes:
Fixes: 812b31d3f91 ("configs: rename default-configs to configs and reorganise")
Signed-off-by: Philippe Mathieu-Daudé
---
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.
Already fixed in Alex's tree:
https://lore.kernel.org/qemu-devel/[email protected]/
Pierrick suggested to repost patch dependencies already queued in
maintainer tree when posting series; while this seem counter
productive it could indeed have saved us time.
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 looked for your series without success, then realized you mentioned
it is "unsent". This patch is still valid then.
Yes.
Why mention unsent work?
To avoid duplicated work.
I'm not sure this thread is making sense o_O
Let's try to figure what you meant here. I'm not racing to get
this patch in nor enjoying duplicating work, but this is the
mailing list rules (due to the intrinsic email workflow latency,
not to mention subscriber processing their INBOX in FIFO mode).
See for example last week at least 3 developers fixed the same
GCC warning issue. Generically, how could we improve that?
Oh :( I already sent various patches about that yesterday :(
I've been picking them into my tree as I went. I may have missed the
odd patch, but I'll fix that.
F: gdbstub/gdb-xml/hexagon*.xml
T: git https://github.com/quic/qemu.git hex-next
Re: [PATCH] MAINTAINERS: Fix hexagon-linux-user.mak path
Markus Armbruster writes: > Philippe Mathieu-Daudé writes: > >> On 20/5/26 14:57, Philippe Mathieu-Daudé wrote: [...] >>> Oh :( I already sent various patches about that yesterday :( > > I've been picking them into my tree as I went. I may have missed the > odd patch, but I'll fix that. Right now I have Philippe Mathieu-Daudé (9): MAINTAINERS: Fix docker/dockerfiles/debian-hexagon-cross.docker path MAINTAINERS: Cover debian-loongarch-cross.docker with LoongArch section MAINTAINERS: Cover debian-xtensa-cross.docker with Xtensa section MAINTAINERS: Cover debian-tricore-cross.docker with TriCore section MAINTAINERS: Cover python.docker with Python library section MAINTAINERS: Fix hexagon-linux-user.mak path MAINTAINERS: Correct scripts/coverity-model.c path MAINTAINERS: Fix s390x storage key/attribute device paths MAINTAINERS: Fix tcg/s390x/ path and about three dozen of my own. Am I missing any of yours?
Re: [PATCH] MAINTAINERS: Fix hexagon-linux-user.mak path
Philippe Mathieu-Daudé writes:
> Fixes: 812b31d3f91 ("configs: rename default-configs to configs and
> reorganise")
> Signed-off-by: Philippe Mathieu-Daudé
> ---
> 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
> F: gdbstub/gdb-xml/hexagon*.xml
> T: git https://github.com/quic/qemu.git hex-next
The file is already covered by
F: configs/targets/*linux-user.mak
under "Linux user". Covering it in more than one section is of course
just fine. But none of the other configs/targets/FOO-linux-user.mak is
similarly covered by "FOO TCG CPUs", or anything other section.
Observation, not objection.
Re: [PATCH] MAINTAINERS: Fix hexagon-linux-user.mak path
Philippe Mathieu-Daudé writes:
> On 20/5/26 14:57, Philippe Mathieu-Daudé wrote:
>> On 20/5/26 14:52, Markus Armbruster wrote:
>>> Philippe Mathieu-Daudé writes:
>>>
Fixes: 812b31d3f91 ("configs: rename default-configs to configs and
reorganise")
Signed-off-by: Philippe Mathieu-Daudé
---
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.
>> Already fixed in Alex's tree:
>> https://lore.kernel.org/qemu-devel/[email protected]/
>> Pierrick suggested to repost patch dependencies already queued in
>> maintainer tree when posting series; while this seem counter
>> productive it could indeed have saved us time.
>>
>>> 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 looked for your series without success, then realized you mentioned
> it is "unsent". This patch is still valid then.
Yes.
> Why mention unsent work?
To avoid duplicated work.
>> Oh :( I already sent various patches about that yesterday :(
I've been picking them into my tree as I went. I may have missed the
odd patch, but I'll fix that.
>>>
F: gdbstub/gdb-xml/hexagon*.xml
T: git https://github.com/quic/qemu.git hex-next
Re: [PATCH] MAINTAINERS: Fix hexagon-linux-user.mak path
On 20/5/26 14:57, Philippe Mathieu-Daudé wrote:
On 20/5/26 14:52, Markus Armbruster wrote:
Philippe Mathieu-Daudé writes:
Fixes: 812b31d3f91 ("configs: rename default-configs to configs and
reorganise")
Signed-off-by: Philippe Mathieu-Daudé
---
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.
Already fixed in Alex's tree:
https://lore.kernel.org/qemu-devel/2026051810.80735-2-
[email protected]/
Pierrick suggested to repost patch dependencies already queued in
maintainer tree when posting series; while this seem counter
productive it could indeed have saved us time.
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 looked for your series without success, then realized you mentioned
it is "unsent". This patch is still valid then. Why mention unsent work?
Oh :( I already sent various patches about that yesterday :(
F: gdbstub/gdb-xml/hexagon*.xml
T: git https://github.com/quic/qemu.git hex-next
Re: [PATCH] MAINTAINERS: Fix hexagon-linux-user.mak path
On 20/5/26 14:52, Markus Armbruster wrote:
Philippe Mathieu-Daudé writes:
Fixes: 812b31d3f91 ("configs: rename default-configs to configs and reorganise")
Signed-off-by: Philippe Mathieu-Daudé
---
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.
Already fixed in Alex's tree:
https://lore.kernel.org/qemu-devel/[email protected]/
Pierrick suggested to repost patch dependencies already queued in
maintainer tree when posting series; while this seem counter
productive it could indeed have saved us time.
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.
Oh :( I already sent various patches about that yesterday :(
F: gdbstub/gdb-xml/hexagon*.xml
T: git https://github.com/quic/qemu.git hex-next
Re: [PATCH] MAINTAINERS: Fix hexagon-linux-user.mak path
Philippe Mathieu-Daudé writes:
> Fixes: 812b31d3f91 ("configs: rename default-configs to configs and
> reorganise")
> Signed-off-by: Philippe Mathieu-Daudé
> ---
> 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.
> F: gdbstub/gdb-xml/hexagon*.xml
> T: git https://github.com/quic/qemu.git hex-next
