From: Igor Mammedov <imammedo@redhat.com>
To: Stefan Hajnoczi <stefanha@redhat.com>
Cc: "Kevin Wolf" <kwolf@redhat.com>, "Fam Zheng" <famz@redhat.com>,
"Michael Roth" <mdroth@linux.vnet.ibm.com>,
qemu-devel@nongnu.org, "Paolo Bonzini" <pbonzini@redhat.com>,
"Andreas Färber" <afaerber@suse.de>
Subject: Re: [Qemu-devel] [PATCH v5 5/7] qdev: make get_pointer() handle temporary strings
Date: Mon, 3 Mar 2014 13:43:09 +0100 [thread overview]
Message-ID: <20140303134309.2f04b9e8@nial.usersys.redhat.com> (raw)
In-Reply-To: <20140303094130.GE4780@stefanha-thinkpad.redhat.com>
On Mon, 3 Mar 2014 10:41:30 +0100
Stefan Hajnoczi <stefanha@redhat.com> wrote:
> On Fri, Feb 28, 2014 at 05:49:09PM +0100, Andreas Färber wrote:
> > Am 28.02.2014 16:18, schrieb Stefan Hajnoczi:
> > > From: Igor Mammedov <imammedo@redhat.com>
> > >
> > > get_pointer()'s print() callback might return a heap allocated
> > > string, to avoid adding dedicated get_pointer_foo for this case
> > > convert current print() callbacks to return temporary heap
> > > allocated string and make get_pointer() free it.
> > >
> > > Signed-off-by: Igor Mammedov <imammedo@redhat.com>
> > > Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
> > > ---
> > > hw/core/qdev-properties-system.c | 19 +++++++++++--------
> > > 1 file changed, 11 insertions(+), 8 deletions(-)
> >
> > Not aware of the history of this patch (not CC'ed?) but looks okay,
> >
> > Reviewed-by: Andreas Färber <afaerber@suse.de>
> >
> > Do we have any users outside of this series?
>
> The patch comes from Igor originally so maybe he has future patches that
> will use it.
>
> Stefan
I don't have other users/plans to use it.
Patch was suggested as alternative to adding a new API:
http://lists.gnu.org/archive/html/qemu-devel/2014-02/msg04704.html
next prev parent reply other threads:[~2014-03-03 12:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-28 15:18 [Qemu-devel] [PATCH v5 0/7] dataplane: switch to N:M devices-per-thread model Stefan Hajnoczi
2014-02-28 15:18 ` [Qemu-devel] [PATCH v5 1/7] object: add object_get_canonical_basename() Stefan Hajnoczi
2014-02-28 17:15 ` Andreas Färber
2014-02-28 18:27 ` Igor Mammedov
2014-03-03 9:52 ` Stefan Hajnoczi
2014-02-28 15:18 ` [Qemu-devel] [PATCH v5 2/7] rfifolock: add recursive FIFO lock Stefan Hajnoczi
2014-02-28 15:18 ` [Qemu-devel] [PATCH v5 3/7] aio: add aio_context_acquire() and aio_context_release() Stefan Hajnoczi
2014-02-28 15:18 ` [Qemu-devel] [PATCH v5 4/7] iothread: add I/O thread object Stefan Hajnoczi
2014-02-28 15:18 ` [Qemu-devel] [PATCH v5 5/7] qdev: make get_pointer() handle temporary strings Stefan Hajnoczi
2014-02-28 16:49 ` Andreas Färber
2014-03-03 9:41 ` Stefan Hajnoczi
2014-03-03 12:43 ` Igor Mammedov [this message]
2014-02-28 15:18 ` [Qemu-devel] [PATCH v5 6/7] iothread: add "iothread" qdev property type Stefan Hajnoczi
2014-02-28 15:18 ` [Qemu-devel] [PATCH v5 7/7] dataplane: replace internal thread with IOThread 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=20140303134309.2f04b9e8@nial.usersys.redhat.com \
--to=imammedo@redhat.com \
--cc=afaerber@suse.de \
--cc=famz@redhat.com \
--cc=kwolf@redhat.com \
--cc=mdroth@linux.vnet.ibm.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@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).