[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] [PATCH v5] nvme: Add tracing

From: Stefan Hajnoczi
Subject: Re: [Qemu-devel] [PATCH v5] nvme: Add tracing
Date: Tue, 28 Nov 2017 10:49:48 +0000
User-agent: Mutt/1.9.1 (2017-09-22)

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: signature.asc
Description: PGP signature

reply via email to

[Prev in Thread] Current Thread [Next in Thread]