All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Philippe Mathieu-Daudé" <f4bug@amsat.org>
To: Thomas Huth <thuth@redhat.com>, Stefan Hajnoczi <stefanha@redhat.com>
Cc: qemu-devel@nongnu.org, qemu-trivial@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] MAINTAINERS: Add trace-events and qemu-option-trace.texi to tracing section
Date: Wed, 9 May 2018 02:02:31 -0300	[thread overview]
Message-ID: <f0a24157-3aa9-4b51-8870-e83407e85697@amsat.org> (raw)
In-Reply-To: <1525840700-30635-1-git-send-email-thuth@redhat.com>

Hi Thomas,

On 05/09/2018 01:38 AM, Thomas Huth wrote:
> The "trace-events" and "qemu-option-trace.texi" files in the top directory
> are currently "unmaintained" according to scripts/get_maintainer.pl. They
> obviously belong to the Tracing section, so add an entry for them there.

I agree qemu-option-trace.texi belongs to the Tracing section,
however I think trace-events is not specific to Tracing but belongs to
everybody maintaining a C file in the top directory... Since they'll
need to modify this file.

> Signed-off-by: Thomas Huth <thuth@redhat.com>
> ---
>  MAINTAINERS | 2 ++
>  1 file changed, 2 insertions(+)
> 
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 459e359..e187b1f 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -1656,6 +1656,8 @@ Tracing
>  M: Stefan Hajnoczi <stefanha@redhat.com>
>  S: Maintained
>  F: trace/
> +F: trace-events

So without "trace-events":
Reviewed-by: Philippe Mathieu-Daudé <f4bug@amsat.org>

> +F: qemu-option-trace.texi
>  F: scripts/tracetool.py
>  F: scripts/tracetool/
>  F: docs/devel/tracing.txt
> 

  reply	other threads:[~2018-05-09  5:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-09  4:38 [Qemu-devel] [PATCH] MAINTAINERS: Add trace-events and qemu-option-trace.texi to tracing section Thomas Huth
2018-05-09  5:02 ` Philippe Mathieu-Daudé [this message]
2018-05-09  5:10   ` Thomas Huth
2018-05-09 12:51   ` Eric Blake
2018-05-10 10:56 ` Stefan Hajnoczi

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=f0a24157-3aa9-4b51-8870-e83407e85697@amsat.org \
    --to=f4bug@amsat.org \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-trivial@nongnu.org \
    --cc=stefanha@redhat.com \
    --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 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.