qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: Eric Blake <eblake@redhat.com>, qemu-devel@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>,
	Stefan Hajnoczi <stefanha@redhat.com>,
	qemu-block@nongnu.org, qemu-trivial@nongnu.org,
	Max Reitz <mreitz@redhat.com>,
	Aleksandar Markovic <amarkovic@wavecomp.com>,
	Aleksandar Rikalo <aleksandar.rikalo@rt-rk.com>,
	Aurelien Jarno <aurelien@aurel32.net>
Subject: Re: [PATCH-for-4.2 v4 0/2] hw: Remove dynamic field width from trace events
Date: Mon, 18 Nov 2019 23:29:50 +0100	[thread overview]
Message-ID: <7b8db299-0d00-d8d2-8612-7f7beccb84bb@redhat.com> (raw)
In-Reply-To: <20191118222746.31467-1-philmd@redhat.com>

This is material for 4.2-rc2.

On 11/18/19 11:27 PM, Philippe Mathieu-Daudé wrote:
> This series fixes LP#1844817 [2].
> 
> (Eric noted in [1] the dtrace via stap backend can not support
> the dynamic '*' width format.)
> 
> If they are trivial/block/tracing pull in preparation, this
> series will be happy to be taken, else it will go via mips-next.
> 
> Thanks,
> 
> Phil.
> 
> [1] https://lists.gnu.org/archive/html/qemu-devel/2019-09/msg04720.html
> [2] https://bugs.launchpad.net/qemu/+bug/1844817



  parent reply	other threads:[~2019-11-18 22:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-18 22:27 [PATCH v4 0/2] hw: Remove dynamic field width from trace events Philippe Mathieu-Daudé
2019-11-18 22:27 ` [PATCH v4 1/2] hw/block/pflash: " Philippe Mathieu-Daudé
2019-11-18 22:27 ` [PATCH v4 2/2] hw/mips/gt64xxx: " Philippe Mathieu-Daudé
2019-11-18 22:29 ` Philippe Mathieu-Daudé [this message]
2019-11-19 16:21 ` [PATCH v4 0/2] hw: " Stefan Hajnoczi
2019-11-19 16:24   ` Philippe Mathieu-Daudé

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=7b8db299-0d00-d8d2-8612-7f7beccb84bb@redhat.com \
    --to=philmd@redhat.com \
    --cc=aleksandar.rikalo@rt-rk.com \
    --cc=amarkovic@wavecomp.com \
    --cc=aurelien@aurel32.net \
    --cc=eblake@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=mreitz@redhat.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-trivial@nongnu.org \
    --cc=stefanha@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).