From: Anthony Liguori <aliguori@us.ibm.com>
To: Luiz Capitulino <lcapitulino@redhat.com>
Cc: Peter Maydell <peter.maydell@linaro.org>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 2/5] boards: rename machine type functions
Date: Fri, 24 Feb 2012 10:57:40 -0600 [thread overview]
Message-ID: <4F47C184.8090503@us.ibm.com> (raw)
In-Reply-To: <20120224145151.53f5e1de@doriath.home>
On 02/24/2012 10:51 AM, Luiz Capitulino wrote:
> On Fri, 24 Feb 2012 10:15:52 -0600
> Anthony Liguori<aliguori@us.ibm.com> wrote:
>
>> On 02/24/2012 10:12 AM, Peter Maydell wrote:
>>> On 24 February 2012 14:13, Luiz Capitulino<lcapitulino@redhat.com> wrote:
>>>> Perform the following renames:
>>>>
>>>> o qemu_register_machine() -> machine_register()
>>>> o find_machine() -> machine_find()
>>>> o find_default_machine() -> machine_find_default()
>>>>
>>>> Signed-off-by: Luiz Capitulino<lcapitulino@redhat.com>
>>>> 52 files changed, 96 insertions(+), 96 deletions(-)
>>>
>>> I said I was going to nack the next change-whole-tree
>>> change, so here it is: nack.
>>>
>>> At some point we're going to have to actually start
>>> converting boards to be QOM objects themselves, but
>>> (a) I hope we can make that incremental so we can do
>>> things in batches the way we did with MemoryRegion
>>> conversions and (b) until then the qemu_register_machine
>>> rename just looks like unnecessary churn to me.
>>
>> I think I agree with you here. I don't see the value compared to the churn here
>> given that we're going to have to touch all of this again anyway soon.
>
> Do you guys see value in patch 5/5, which moves the machine function to the
> boards file?
Yes. And it's not that the other practicals aren't useful, it's just that I
agree with Peter's valid point that the churn outweighs the benefit right now.
Regards,
Anthony Liguori
>
> If you don't I'll keep only patch 1/5 (which can be submitted to qemu-trivial).
>
next prev parent reply other threads:[~2012-02-24 16:59 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-24 14:13 [Qemu-devel] [PATCH 0/5]: Improve machine type functions Luiz Capitulino
2012-02-24 14:13 ` [Qemu-devel] [PATCH 1/5] boards: qemu_register_machine(): return void Luiz Capitulino
2012-02-24 14:17 ` Andreas Färber
2012-02-24 14:13 ` [Qemu-devel] [PATCH 2/5] boards: rename machine type functions Luiz Capitulino
2012-02-24 16:12 ` Peter Maydell
2012-02-24 16:15 ` Anthony Liguori
2012-02-24 16:51 ` Luiz Capitulino
2012-02-24 16:57 ` Anthony Liguori [this message]
2012-02-24 14:13 ` [Qemu-devel] [PATCH 3/5] boards: introduce machine_print_all() Luiz Capitulino
2012-02-24 14:26 ` Andreas Färber
2012-02-24 14:57 ` Luiz Capitulino
2012-02-24 14:13 ` [Qemu-devel] [PATCH 4/5] boards: switch machine type list to QTAILQ Luiz Capitulino
2012-02-24 14:23 ` Andreas Färber
2012-02-24 14:56 ` Luiz Capitulino
2012-02-24 15:21 ` Andreas Färber
2012-02-24 15:23 ` Luiz Capitulino
2012-02-24 14:13 ` [Qemu-devel] [PATCH 5/5] boards: move all machine type functions to boards.c Luiz Capitulino
2012-02-24 15:10 ` Andreas Färber
2012-02-24 15:22 ` Luiz Capitulino
2012-02-24 14:58 ` [Qemu-devel] [PATCH 0/5]: Improve machine type functions Anthony Liguori
2012-02-24 15:20 ` Luiz Capitulino
2012-02-24 15:44 ` Anthony Liguori
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=4F47C184.8090503@us.ibm.com \
--to=aliguori@us.ibm.com \
--cc=lcapitulino@redhat.com \
--cc=peter.maydell@linaro.org \
--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).