From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: Thomas Huth <thuth@redhat.com>, qemu-devel@nongnu.org
Cc: "Daniel P . Berrange" <berrange@redhat.com>, qemu-arm@nongnu.org
Subject: Re: [PATCH] MAINTAINERS: Add functional tests that are not covered yet
Date: Mon, 14 Apr 2025 18:11:23 +0200 [thread overview]
Message-ID: <a8d305e6-3658-4ee6-98dd-167b41a184cd@linaro.org> (raw)
In-Reply-To: <20250414121520.213665-1-thuth@redhat.com>
On 14/4/25 14:15, Thomas Huth wrote:
> From: Thomas Huth <thuth@redhat.com>
>
> Some functional tests are currently not covered by the entries
> in MAINTAINERS yet, so scripts/get_maintainers.pl fails to suggest
> the right people who should be CC:-ed for related patches.
> Add the uncovered tests to the right sections to close this gap.
>
> Signed-off-by: Thomas Huth <thuth@redhat.com>
> ---
> MAINTAINERS | 13 +++++++++++--
> 1 file changed, 11 insertions(+), 2 deletions(-)
Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org>
prev parent reply other threads:[~2025-04-14 16:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-14 12:15 [PATCH] MAINTAINERS: Add functional tests that are not covered yet Thomas Huth
2025-04-14 16:11 ` Philippe Mathieu-Daudé [this message]
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=a8d305e6-3658-4ee6-98dd-167b41a184cd@linaro.org \
--to=philmd@linaro.org \
--cc=berrange@redhat.com \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).