qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: Amit Shah <amit.shah@redhat.com>
Cc: qemu list <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH 1/1] char: Add a QemuChrHandlers struct to initialise chardev handlers
Date: Fri, 10 Feb 2012 11:22:20 -0600	[thread overview]
Message-ID: <4F35524C.5070303@codemonkey.ws> (raw)
In-Reply-To: <20120210170903.GA475@amit.redhat.com>

On 02/10/2012 11:09 AM, Amit Shah wrote:
> On (Fri) 10 Feb 2012 [07:28:19], Anthony Liguori wrote:
>> On 02/10/2012 07:19 AM, Amit Shah wrote:
>>> Instead of passing each handler in the qemu_add_handlers() function,
>>> create a struct of handlers that can be passed to the function instead.
>>>
>>> Signed-off-by: Amit Shah<amit.shah@redhat.com>
>>
>> Why?
>
> It's a good cleanup.
>
>> It's not a win in terms of code size.  If you plan on introducing
>> additional handlers, perhaps you should include this in that series
>> where it's more appropriately justified.
>>
>> As a change on it's own, it doesn't seem to make a lot of sense.
>
> Makes the code much easier to look at.  Can't really compare on code
> size, since there's zero change in the resulting binary, but the code
> just becomes more readable and manageable.

It's not more readable IMHO.  You've taken function call arguments from the 
place they naturally belong (in the function call) and placed them somewhere else.

More importantly, this isn't a pattern we use in QEMU anywhere.

Regards,

Anthony Liguori

>
> 		Amit

  reply	other threads:[~2012-02-10 17:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-10 13:19 [Qemu-devel] [PATCH 1/1] char: Add a QemuChrHandlers struct to initialise chardev handlers Amit Shah
2012-02-10 13:28 ` Anthony Liguori
2012-02-10 17:09   ` Amit Shah
2012-02-10 17:22     ` Anthony Liguori [this message]
2012-02-10 18:08       ` Kevin Wolf
2012-02-10 18:18         ` 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=4F35524C.5070303@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=amit.shah@redhat.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 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).