From: Chris Ball <cjb@laptop.org>
To: Venkatraman S <svenkatr@ti.com>
Cc: linux-mmc@vger.kernel.org, linkinjeon@gmail.com,
jh80.chung@samsung.com, alex.lemberg@sandisk.com,
Kostya <kdorfman@codeaurora.org>
Subject: Re: [PATCH v3] mmc: core: Fix the HPI execution sequence
Date: Wed, 20 Jun 2012 13:01:06 -0400 [thread overview]
Message-ID: <87y5nh3okt.fsf@octavius.laptop.org> (raw)
In-Reply-To: <1340184834-12700-1-git-send-email-svenkatr@ti.com> (Venkatraman S.'s message of "Wed, 20 Jun 2012 15:03:54 +0530")
Hi, trivial style comments,
On Wed, Jun 20 2012, Venkatraman S wrote:
> switch (R1_CURRENT_STATE(status)) {
>
No newline here.
> case R1_STATE_IDLE:
> case R1_STATE_READY:
> case R1_STATE_STBY: /* intentional fall through */
> /* In idle states, HPI is not needed and the caller
> can issue the next intended command immediately */
> goto out;
> break;
This might just be personal style, but I don't think of this as
"intentional fall through" -- you're just matching multiple cases.
Case fall-through would be if the code inside the cases didn't call
goto or break at the end and kept going into the next code block,
which doesn't happen here. Here's an elegant use of fall-through:
http://chris.printf.net/btrfs_parse_size.txt
I don't think you should bother using break after you've already
called goto.
Also, please use:
/*
* comment 1
* comment 2
*/
for multiline comments instead of
/* comment 1
comment 2 */
Thanks!
- Chris.
--
Chris Ball <cjb@laptop.org> <http://printf.net/>
One Laptop Per Child
next prev parent reply other threads:[~2012-06-20 17:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-20 9:33 [PATCH v3] mmc: core: Fix the HPI execution sequence Venkatraman S
2012-06-20 17:01 ` Chris Ball [this message]
2012-06-20 17:55 ` S, Venkatraman
2012-06-20 17:59 ` Subhash Jadavani
2012-06-21 7:24 ` S, Venkatraman
2012-06-21 11:08 ` Subhash Jadavani
2012-06-21 13:16 ` S, Venkatraman
2012-06-21 14:13 ` [PATCH v4] " Venkatraman S
2012-06-21 15:37 ` Subhash Jadavani
2012-06-22 6:12 ` [PATCH v5] " Venkatraman S
2012-06-22 13:31 ` Subhash Jadavani
2012-06-28 7:42 ` S, Venkatraman
2012-06-28 7:45 ` S, Venkatraman
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=87y5nh3okt.fsf@octavius.laptop.org \
--to=cjb@laptop.org \
--cc=alex.lemberg@sandisk.com \
--cc=jh80.chung@samsung.com \
--cc=kdorfman@codeaurora.org \
--cc=linkinjeon@gmail.com \
--cc=linux-mmc@vger.kernel.org \
--cc=svenkatr@ti.com \
/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