From: Chen Gang <gang.chen.5i5j@gmail.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: QEMU Developers <qemu-devel@nongnu.org>, aliguori@amazon.com
Subject: Re: [Qemu-devel] [PATCH trival] vl.c: clean up code
Date: Tue, 01 Apr 2014 21:42:08 +0800 [thread overview]
Message-ID: <533AC230.3050404@gmail.com> (raw)
In-Reply-To: <87vbuti37t.fsf@blackfin.pond.sub.org>
On 04/01/2014 09:33 PM, Markus Armbruster wrote:
> Chen Gang <gang.chen.5i5j@gmail.com> writes:
>
>> On 04/01/2014 04:13 PM, Markus Armbruster wrote:
>>> Chen Gang <gang.chen.5i5j@gmail.com> writes:
>>>
>>>> On 03/31/2014 11:49 PM, Markus Armbruster wrote:
>>>>> Chen Gang <gang.chen.5i5j@gmail.com> writes:
>>>>>
>>>>>> in get_boot_device()
>>>>>>
>>>>>> - remove 'res' to simplify code
>>>>>>
>>>>>> in main():
>>>>>>
>>>>>> - remove useless 'continue'.
>>>>>>
>>>>>> - in main switch():
>>>>>>
>>>>>> - remove or adjust all useless 'break'.
>>>>>>
>>>>>> - remove useless '{' and '}'.
>>>>>>
>>>>>> - use assignment directly to replace useless 'args'
>>>>>> (which is defined in the middle of code block).
>>>>>
>>>>> Suggest to have one patch per item in this list.
>>>>>
>>>>
>>>> OK, thanks. I will/should send again in this week (within 2014-04-06).
>>>
>>> No rush :)
>>>
>>
>> Yeah, more discussions, and more thinking of, before implementations.
>
> What I meant to say is "next week is fine, we're not in a big hurry to
> get this done".
>
OK, thanks. :-)
Thanks.
--
Chen Gang
Open, share, and attitude like air, water, and life which God blessed
prev parent reply other threads:[~2014-04-01 13:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-30 14:34 [Qemu-devel] [PATCH trival] vl.c: clean up code Chen Gang
2014-03-30 14:43 ` Chen Gang
2014-04-01 12:36 ` Alex Bennée
2014-04-01 13:08 ` Chen Gang
2014-03-31 15:49 ` Markus Armbruster
2014-04-01 0:11 ` Chen Gang
2014-04-01 8:13 ` Markus Armbruster
2014-04-01 9:01 ` Chen Gang
2014-04-01 13:33 ` Markus Armbruster
2014-04-01 13:42 ` Chen Gang [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=533AC230.3050404@gmail.com \
--to=gang.chen.5i5j@gmail.com \
--cc=aliguori@amazon.com \
--cc=armbru@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).