From: Eric Blake <eblake@redhat.com>
To: David Gibson <david@gibson.dropbear.id.au>,
Markus Armbruster <armbru@redhat.com>
Cc: qemu-ppc@nongnu.org, qemu-devel@nongnu.org, agraf@suse.de
Subject: Re: [Qemu-devel] Posible regressions around spapr-dr-connector property drc-connector[]
Date: Mon, 7 Dec 2015 17:24:14 -0700 [thread overview]
Message-ID: <5666232E.7040302@redhat.com> (raw)
In-Reply-To: <20151208001802.GF20139@voom.fritz.box>
[-- Attachment #1: Type: text/plain, Size: 1253 bytes --]
On 12/07/2015 05:18 PM, David Gibson wrote:
> On Fri, Dec 04, 2015 at 11:11:31AM +0100, Markus Armbruster wrote:
>> David Gibson <david@gibson.dropbear.id.au> writes:
>>
>>>> It was {} in 2.4. Changing it to null so we can distingish "nothing"
>>>> from "empty" is an incompatible change. May make sense anyway, but I
>>>> can't judge it.
>>>
>>> Strictly speaking it's an incompatible change, yes. But I find it
>>> hard to imagine anything would be relying on the {} behaviour. This
>>> property is essentially a debugging interface to start with, and the
>>> missing / empty case is examining it in a state that's unlikely to be
>>> interesting.
>>
>> I'm not against changing it, I just want it changed intentionally rather
>> than by accidental side effect :)
>>
>> If you tell me you want null here going forward, I'll make sure it gets
>> changed to null in the next development cycle, with a nice commit
>> message.
>
> I would like it to be null (or simply missing) in future.
Okay, I'm about to post the patch for just that, for the 2.6 timeframe.
> But leaving it as is for 2.5 is fine.
Good.
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]
prev parent reply other threads:[~2015-12-08 0:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-03 15:30 [Qemu-devel] Posible regressions around spapr-dr-connector property drc-connector[] Markus Armbruster
2015-12-04 0:01 ` David Gibson
2015-12-04 8:05 ` Markus Armbruster
2015-12-04 9:35 ` David Gibson
2015-12-04 10:11 ` Markus Armbruster
2015-12-04 11:52 ` Peter Maydell
2015-12-08 0:18 ` David Gibson
2015-12-08 0:24 ` Eric Blake [this message]
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=5666232E.7040302@redhat.com \
--to=eblake@redhat.com \
--cc=agraf@suse.de \
--cc=armbru@redhat.com \
--cc=david@gibson.dropbear.id.au \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@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).