qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Chen Gang <gang.chen.5i5j@gmail.com>
To: "Alex Bennée" <alex.bennee@linaro.org>
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:08:28 +0800	[thread overview]
Message-ID: <533ABA4C.7090001@gmail.com> (raw)
In-Reply-To: <87ha6drzth.fsf@linaro.org>

On 04/01/2014 08:36 PM, Alex Bennée wrote:
> 
> Chen Gang <gang.chen.5i5j@gmail.com> writes:
> 
>> Hello Maintainers:
>>
>> In main switch of main(), it contents several styles for "{...}" code block.
>>
>> If it is necessary to use unique style within a function, please let me
>> know, I will/should clean up it. And also better to tell me which style
>> we need choose -- for me, I don't know which style is the best to
>> Qemu.
> 
> The correct block style is described in CODING_STYLE Section 4. However
> chunks of the code base violate the style guidelines and should be
> cleaned up as other fixes are made.
> 

In CODING_STYLE Section 4, has no demo for "{...}" within switch, I
guess your meaning is "the demo below is the correct block style for Qemu":

	switch(...) {
	case 'x': {
		char a;
		...
		break;
	}
	case 'y':
		...
		break;
	default:
		break;
	}

If it is OK, suggest to complete the CODING_STYLE Section 4 with one
'switch' demo.


Thanks.
-- 
Chen Gang

Open, share, and attitude like air, water, and life which God blessed

  reply	other threads:[~2014-04-01 13:08 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 [this message]
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

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=533ABA4C.7090001@gmail.com \
    --to=gang.chen.5i5j@gmail.com \
    --cc=alex.bennee@linaro.org \
    --cc=aliguori@amazon.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).