qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Laszlo Ersek <lersek@redhat.com>
To: Thomas Huth <thuth@redhat.com>, qemu-devel@nongnu.org
Cc: Laurent Vivier <lvivier@redhat.com>, Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [PATCH] MAINTAINERS: Ignore bios-tables-test in the qtest section
Date: Thu, 1 Oct 2020 15:15:42 +0200	[thread overview]
Message-ID: <a49014f1-0fed-74d0-85c3-a8bfc91e26ab@redhat.com> (raw)
In-Reply-To: <20201001042717.136033-1-thuth@redhat.com>

On 10/01/20 06:27, Thomas Huth wrote:
> I'm very often getting CC: on rather large patch series that
> modify the ACPI stuff of either ARM or x86, just because the
> bios-table-test is often slightly involved here. I can't say
> much about ACPI, and the bios-table-test is already covered
> by the ACPI section in MAINTAINERS,

Right, the exact same pattern that you're going to exclude in this patch
from under "qtest" is already covered under "ACPI/SMBIOS":

F: tests/qtest/bios-tables-test*

> so I'd rather prefer to
> not getting automatically CC-ed on such patch series anymore.
> If people want my opinion about qtest-related changes, they
> can still put me on CC manually.
> 
> Signed-off-by: Thomas Huth <thuth@redhat.com>
> ---
>  MAINTAINERS | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/MAINTAINERS b/MAINTAINERS
> index e1e8ae277d..d476fbf627 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -2474,7 +2474,7 @@ S: Maintained
>  F: softmmu/qtest.c
>  F: accel/qtest.c
>  F: tests/qtest/
> -X: tests/qtest/bios-tables-test-allowed-diff.h
> +X: tests/qtest/bios-tables-test*
>  
>  Device Fuzzing
>  M: Alexander Bulekov <alxndr@bu.edu>
> 

FWIW:

Acked-by: Laszlo Ersek <lersek@redhat.com>

Thanks
Laszlo



      reply	other threads:[~2020-10-01 13:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-01  4:27 [PATCH] MAINTAINERS: Ignore bios-tables-test in the qtest section Thomas Huth
2020-10-01 13:15 ` Laszlo Ersek [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=a49014f1-0fed-74d0-85c3-a8bfc91e26ab@redhat.com \
    --to=lersek@redhat.com \
    --cc=lvivier@redhat.com \
    --cc=pbonzini@redhat.com \
    --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).