From: Markus Armbruster <armbru@redhat.com>
To: "Philippe Mathieu-Daudé" <philmd@linaro.org>
Cc: qemu-devel@nongnu.org,
Pierrick Bouvier <pierrick.bouvier@oss.qualcomm.com>,
Brian Cain <brian.cain@oss.qualcomm.com>
Subject: Re: [PATCH] MAINTAINERS: Fix hexagon-linux-user.mak path
Date: Wed, 20 May 2026 15:44:41 +0200 [thread overview]
Message-ID: <87se7mjiuu.fsf@pond.sub.org> (raw)
In-Reply-To: <87fr3mkz26.fsf@pond.sub.org> (Markus Armbruster's message of "Wed, 20 May 2026 15:09:21 +0200")
Markus Armbruster <armbru@redhat.com> writes:
> Philippe Mathieu-Daudé <philmd@linaro.org> 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?
next prev parent reply other threads:[~2026-05-20 13:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-20 12:39 [PATCH] MAINTAINERS: Fix hexagon-linux-user.mak path Philippe Mathieu-Daudé
2026-05-20 12:52 ` Markus Armbruster
2026-05-20 12:57 ` Philippe Mathieu-Daudé
2026-05-20 12:59 ` Philippe Mathieu-Daudé
2026-05-20 13:09 ` Markus Armbruster
2026-05-20 13:44 ` Markus Armbruster [this message]
2026-05-20 14:05 ` Philippe Mathieu-Daudé
2026-05-20 14:43 ` Markus Armbruster
2026-05-20 15:13 ` Pierrick Bouvier
2026-05-20 17:28 ` Pierrick Bouvier
2026-05-20 18:10 ` Markus Armbruster
2026-05-20 13:38 ` Markus Armbruster
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87se7mjiuu.fsf@pond.sub.org \
--to=armbru@redhat.com \
--cc=brian.cain@oss.qualcomm.com \
--cc=philmd@linaro.org \
--cc=pierrick.bouvier@oss.qualcomm.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.