From: Alexey Kardashevskiy <aik@ozlabs.ru>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] ohci: Fix compile errors without --enable-trace-backend
Date: Thu, 25 Sep 2014 10:17:49 +1000 [thread overview]
Message-ID: <54235F2D.5070605@ozlabs.ru> (raw)
In-Reply-To: <1411469555.16260.3.camel@nilsson.home.kraxel.org>
On 09/23/2014 08:52 PM, Gerd Hoffmann wrote:
> On Di, 2014-09-23 at 20:19 +1000, Alexey Kardashevskiy wrote:
>> This adds a stub for ohci_td_pkt() function (which traces packets)
>> when configured without --enable-trace-backend
>
> Ah, cool. Just noticed that, while doing usb patch queue test builds
> for the next pull req.
>
>> It should probably be squashed to
>> [PATCH] ohci: Convert fprint/DPRINTF/print to traces
>
> Done.
Posted another patch for dtrace backend... Sorry for too much noise.
--
Alexey
next prev parent reply other threads:[~2014-09-25 0:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-23 10:19 [Qemu-devel] [PATCH] ohci: Fix compile errors without --enable-trace-backend Alexey Kardashevskiy
2014-09-23 10:52 ` Gerd Hoffmann
2014-09-25 0:17 ` Alexey Kardashevskiy [this message]
2014-09-24 9:47 ` Stefan Hajnoczi
2014-09-25 0:19 ` Alexey Kardashevskiy
2014-09-26 8:32 ` 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=54235F2D.5070605@ozlabs.ru \
--to=aik@ozlabs.ru \
--cc=kraxel@redhat.com \
--cc=qemu-devel@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).