Hi Markus,
On 3/6/26 08:39, Markus Armbruster wrote:
> Quite a few F: lines don't match any files. The quick & dirty check
>
> $ ls `sed -n 's/^F: *//p' MAINTAINERS ` >/dev/null
>
> finds about fifty.
>
> Philippe Mathieu-Daudé recently posted a few fixes:
>
> 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 s390x storage key/attribute device paths
> MAINTAINERS: Fix tcg/s390x/ path
> MAINTAINERS: Correct scripts/coverity-model.c path
> MAINTAINERS: Fix RISCV related paths
> MAINTAINERS: Fix hexagon-linux-user.mak path
>
> These are in
>
> Subject: [PATCH 0/7] docker: Remove LegacyKeyValueFormat warnings
> Date: Mon, 18 May 2026 12:22:15 +0200
> Message-ID: <20260518102222.80735-1-philmd@linaro.org>
>
> Subject: [PATCH v2 0/4] buildsys: Stop checking for ESA/390 host
> Date: Tue, 19 May 2026 19:12:36 +0200
> Message-ID: <20260519171240.97420-1-philmd@linaro.org>
>
> Subject: [PATCH] MAINTAINERS: Correct scripts/coverity-model.c path
> Date: Tue, 19 May 2026 19:19:26 +0200
> Message-ID: <20260519171926.98099-1-philmd@linaro.org>
>
> Subject: [PATCH] MAINTAINERS: Fix RISCV related paths
> Date: Tue, 19 May 2026 19:26:21 +0200
> Message-ID: <20260519172621.98469-1-philmd@linaro.org>
>
> Subject: [PATCH] MAINTAINERS: Fix hexagon-linux-user.mak path
> Date: Wed, 20 May 2026 14:39:47 +0200
> Message-ID: <20260520123947.12711-1-philmd@linaro.org>
>
> This series takes care of the remainder, except for one discussed
> next. It applies cleanly with and without Philippe's patches.
Not sure if you are expecting something from me here, I dropped
these thinking you'd include them in your cleanup series or in
a PR.
Friendly recommendation: merge what is already review and repost
what is not in 1 week, do not wait for all the 38 patches to be
reviewed before posting your PR, that'd be exhausting. Or even,
do not repost in 1 week, directly send your PR; these patches
have been long enough on the list.
Regards,
Phil.