From: Luiz Capitulino <lcapitulino@redhat.com>
To: Prerna Saxena <prerna@linux.vnet.ibm.com>
Cc: qemu-devel@nongnu.org, Anthony Liguori <aliguori@us.ibm.com>,
Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>,
kvm@vger.kernel.org, Jan Kiszka <jan.kiszka@siemens.com>,
maneesh@linux.vnet.ibm.com, ananth@linux.vnet.ibm.com
Subject: Re: [RFC v2] [PATCH 1/3] Export tdb_hash()
Date: Fri, 11 Jun 2010 14:54:33 -0300 [thread overview]
Message-ID: <20100611145433.669a14ab@redhat.com> (raw)
In-Reply-To: <20100611004558.7d87f0e5@zephyr>
On Fri, 11 Jun 2010 00:45:58 +0530
Prerna Saxena <prerna@linux.vnet.ibm.com> wrote:
> For now, I simply export tdb_hash() from qdict.h for use by tracing
> framework.
> Luiz suggested renaming and exporting it from a location other than
> qdict.h . Would "qemu-common.h" be a better place?
qemu-common.h seems to be about header files, I thought we had a qemu-misc.c
file already. I'd create it if we don't.
WARNING: multiple messages have this Message-ID (diff)
From: Luiz Capitulino <lcapitulino@redhat.com>
To: Prerna Saxena <prerna@linux.vnet.ibm.com>
Cc: Anthony Liguori <aliguori@us.ibm.com>,
Hajnoczi <stefanha@linux.vnet.ibm.com>,
kvm@vger.kernel.org, Jan Kiszka <jan.kiszka@siemens.com>,
Stefan@gnu.org, qemu-devel@nongnu.org,
maneesh@linux.vnet.ibm.com, ananth@linux.vnet.ibm.com
Subject: [Qemu-devel] Re: [RFC v2] [PATCH 1/3] Export tdb_hash()
Date: Fri, 11 Jun 2010 14:54:33 -0300 [thread overview]
Message-ID: <20100611145433.669a14ab@redhat.com> (raw)
In-Reply-To: <20100611004558.7d87f0e5@zephyr>
On Fri, 11 Jun 2010 00:45:58 +0530
Prerna Saxena <prerna@linux.vnet.ibm.com> wrote:
> For now, I simply export tdb_hash() from qdict.h for use by tracing
> framework.
> Luiz suggested renaming and exporting it from a location other than
> qdict.h . Would "qemu-common.h" be a better place?
qemu-common.h seems to be about header files, I thought we had a qemu-misc.c
file already. I'd create it if we don't.
next prev parent reply other threads:[~2010-06-11 17:54 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-10 19:08 [RFC v2] [PATCH 0/3] Monitor Support for 'simple' trace backend Prerna Saxena
2010-06-10 19:08 ` [Qemu-devel] " Prerna Saxena
2010-06-10 19:15 ` [RFC v2] [PATCH 1/3] Export tdb_hash() Prerna Saxena
2010-06-10 19:15 ` [Qemu-devel] " Prerna Saxena
2010-06-11 17:54 ` Luiz Capitulino [this message]
2010-06-11 17:54 ` [Qemu-devel] " Luiz Capitulino
2010-06-10 19:20 ` [RFC v2] [PATCH 2/3] Monitor command 'info trace' Prerna Saxena
2010-06-10 19:20 ` [Qemu-devel] " Prerna Saxena
2010-06-10 19:24 ` [RFC v2] [PATCH 3/3] Toggle tracepoint state Prerna Saxena
2010-06-10 19:24 ` [Qemu-devel] " Prerna Saxena
2010-06-11 11:42 ` [Qemu-devel] [RFC v2] [PATCH 0/3] Monitor Support for 'simple' trace backend Markus Armbruster
2010-06-11 11:42 ` Markus Armbruster
2010-06-11 12:08 ` Jan Kiszka
2010-06-11 12:08 ` Jan Kiszka
2010-06-11 17:56 ` Luiz Capitulino
2010-06-11 17:56 ` Luiz Capitulino
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=20100611145433.669a14ab@redhat.com \
--to=lcapitulino@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=ananth@linux.vnet.ibm.com \
--cc=jan.kiszka@siemens.com \
--cc=kvm@vger.kernel.org \
--cc=maneesh@linux.vnet.ibm.com \
--cc=prerna@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@linux.vnet.ibm.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.