From: "Andreas Färber" <afaerber@suse.de>
To: Pavel Fedin <p.fedin@samsung.com>,
'Peter Crosthwaite' <peter.crosthwaite@xilinx.com>
Cc: 'QEMU Developers' <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH v3] QOM: object_property_add() performance improvement
Date: Fri, 03 Jul 2015 15:24:46 +0200 [thread overview]
Message-ID: <55968D1E.9030308@suse.de> (raw)
In-Reply-To: <015e01d0b593$1a754f60$4f5fee20$@samsung.com>
Am 03.07.2015 um 15:20 schrieb Pavel Fedin:
>> Ping!
>
> May be you could PULL it? Andreas seems to be down...
Nack, I don't like the patch as is. Starting with the unoptimized code
movement combined with functional changes, up to the use of [*] for the
new property iiuc.
Andreas
--
SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Dilip Upmanyu, Graham Norton; HRB
21284 (AG Nürnberg)
next prev parent reply other threads:[~2015-07-03 13:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-16 7:50 [Qemu-devel] [PATCH v3] QOM: object_property_add() performance improvement Pavel Fedin
2015-06-27 3:27 ` Peter Crosthwaite
2015-06-29 6:32 ` Pavel Fedin
2015-07-03 13:20 ` Pavel Fedin
2015-07-03 13:24 ` Andreas Färber [this message]
2015-07-03 13:38 ` Pavel Fedin
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=55968D1E.9030308@suse.de \
--to=afaerber@suse.de \
--cc=p.fedin@samsung.com \
--cc=peter.crosthwaite@xilinx.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 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.