From: "Alex Bennée" <alex.bennee@linaro.org>
To: "Richard W.M. Jones" <rjones@redhat.com>
Cc: qemu-trivial@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [Qemu-trivial] [Qemu-devel] [PATCH] docs: Update documentation for stderr (now log) tracing backend.
Date: Mon, 21 Mar 2016 09:16:38 +0000 [thread overview]
Message-ID: <87twk0ry15.fsf@linaro.org> (raw)
In-Reply-To: <1458507614-32470-1-git-send-email-rjones@redhat.com>
Richard W.M. Jones <rjones@redhat.com> writes:
> This fixes commit ed7f5f1d8db06fc31352a5ef4f54985e630c575a.
>
> Signed-off-by: Richard W.M. Jones.
> Cc: Paolo Bonzini <pbonzini@redhat.com>
> Cc: Stefan Hajnoczi <stefanha@redhat.com>
Reviewed-by: Alex Bennée <alex.bennee@linaro.org>
> ---
> docs/tracing.txt | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/docs/tracing.txt b/docs/tracing.txt
> index 3182ee8..0bd6b9c 100644
> --- a/docs/tracing.txt
> +++ b/docs/tracing.txt
> @@ -157,9 +157,9 @@ performance penalty.
> Note that regardless of the selected trace backend, events with the "disable"
> property will be generated with the "nop" backend.
>
> -=== Stderr ===
> +=== Log ===
>
> -The "stderr" backend sends trace events directly to standard error. This
> +The "log" backend sends trace events directly to standard error. This
> effectively turns trace events into debug printfs.
>
> This is the simplest backend and can be used together with existing code that
--
Alex Bennée
WARNING: multiple messages have this Message-ID (diff)
From: "Alex Bennée" <alex.bennee@linaro.org>
To: "Richard W.M. Jones" <rjones@redhat.com>
Cc: qemu-trivial@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] docs: Update documentation for stderr (now log) tracing backend.
Date: Mon, 21 Mar 2016 09:16:38 +0000 [thread overview]
Message-ID: <87twk0ry15.fsf@linaro.org> (raw)
In-Reply-To: <1458507614-32470-1-git-send-email-rjones@redhat.com>
Richard W.M. Jones <rjones@redhat.com> writes:
> This fixes commit ed7f5f1d8db06fc31352a5ef4f54985e630c575a.
>
> Signed-off-by: Richard W.M. Jones.
> Cc: Paolo Bonzini <pbonzini@redhat.com>
> Cc: Stefan Hajnoczi <stefanha@redhat.com>
Reviewed-by: Alex Bennée <alex.bennee@linaro.org>
> ---
> docs/tracing.txt | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/docs/tracing.txt b/docs/tracing.txt
> index 3182ee8..0bd6b9c 100644
> --- a/docs/tracing.txt
> +++ b/docs/tracing.txt
> @@ -157,9 +157,9 @@ performance penalty.
> Note that regardless of the selected trace backend, events with the "disable"
> property will be generated with the "nop" backend.
>
> -=== Stderr ===
> +=== Log ===
>
> -The "stderr" backend sends trace events directly to standard error. This
> +The "log" backend sends trace events directly to standard error. This
> effectively turns trace events into debug printfs.
>
> This is the simplest backend and can be used together with existing code that
--
Alex Bennée
next prev parent reply other threads:[~2016-03-21 9:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-20 21:00 [Qemu-trivial] [PATCH] docs: Update documentation for stderr (now log) tracing backend Richard W.M. Jones
2016-03-20 21:00 ` [Qemu-devel] " Richard W.M. Jones
2016-03-21 9:16 ` Alex Bennée [this message]
2016-03-21 9:16 ` Alex Bennée
2016-03-21 13:50 ` [Qemu-trivial] " Stefan Hajnoczi
2016-03-21 13:50 ` 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=87twk0ry15.fsf@linaro.org \
--to=alex.bennee@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.org \
--cc=rjones@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.