From: Stefan Hajnoczi <stefanha@redhat.com>
To: Kevin Wolf <kwolf@redhat.com>
Cc: "Doug Gale" <doug16k@gmail.com>,
qemu-devel <qemu-devel@nongnu.org>,
qemu-block@nongnu.org, "Keith Busch" <keith.busch@intel.com>,
pbonzini@redhat.com, "Max Reitz" <mreitz@redhat.com>,
"Markus Armbruster" <armbru@redhat.com>,
"Peter Maydell" <peter.maydell@linaro.org>,
"Philippe Mathieu-Daudé" <f4bug@amsat.org>,
"QEMU Trivial" <qemu-trivial@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH v5] nvme: Add tracing
Date: Tue, 28 Nov 2017 10:49:48 +0000 [thread overview]
Message-ID: <20171128104948.GF17146@stefanha-x1.localdomain> (raw)
In-Reply-To: <20171127115832.GC4903@localhost.localdomain>
[-- Attachment #1: Type: text/plain, Size: 752 bytes --]
On Mon, Nov 27, 2017 at 12:58:32PM +0100, Kevin Wolf wrote:
> Am 25.11.2017 um 08:08 hat Doug Gale geschrieben:
> > Ping
>
> Stefan, do you expect this to go through a different tree than the
> tracing one?
Yes, patches that just add/remove/modify trace events go through the
affected component's tree rather than the tracing tree.
For example, the most recent patch was commit
a2e6ffab97e57f823b6bf15371920c6901bb7cbc ("ioapic/tracing: Remove last
DPRINTFs"). It went through Paolo for the PC chipset tree.
Please take this patch via the nvme -> block tree.
One reason to do it this way is that conflicts happen frequently if
trace events changes go through the tracing tree while there are other
patches queued in your tree.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 455 bytes --]
next prev parent reply other threads:[~2017-11-28 10:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-03 13:37 [Qemu-devel] [PATCH v5] nvme: Add tracing Doug Gale
2017-11-03 15:58 ` Philippe Mathieu-Daudé
2017-11-16 11:16 ` Doug Gale
2017-11-25 7:08 ` Doug Gale
2017-11-27 11:58 ` Kevin Wolf
2017-11-28 10:49 ` Stefan Hajnoczi [this message]
2017-12-15 11:16 ` Kevin Wolf
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=20171128104948.GF17146@stefanha-x1.localdomain \
--to=stefanha@redhat.com \
--cc=armbru@redhat.com \
--cc=doug16k@gmail.com \
--cc=f4bug@amsat.org \
--cc=keith.busch@intel.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@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 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).