From: Joe Perches <joe@perches.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Pol Eyschen <poleyschen@gmail.com>,
sachin.kamat@linaro.org, jack@suse.cz, ufimtseva@gmail.com,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
Pol Eyschen <poleyschen@hotmail.com>
Subject: Re: [PATCH] Staging: ced1401: fix coding style in ced_ioc.c
Date: Mon, 13 Jan 2014 18:19:38 -0800 [thread overview]
Message-ID: <1389665978.24849.27.camel@joe-AO722> (raw)
In-Reply-To: <20140113235650.GA23380@kroah.com>
On Mon, 2014-01-13 at 15:56 -0800, Greg KH wrote:
> On Mon, Jan 13, 2014 at 08:41:40PM +0100, Pol Eyschen wrote:
[]
> > diff --git a/drivers/staging/ced1401/ced_ioc.c b/drivers/staging/ced1401/ced_ioc.c
[]
> > @@ -41,7 +41,8 @@ static void FlushOutBuff(DEVICE_EXTENSION *pdx)
> > {
> > dev_dbg(&pdx->interface->dev, "%s currentState=%d", __func__,
> > pdx->sCurrentState);
> > - if (pdx->sCurrentState == U14ERR_TIME) /* Do nothing if hardware in trouble */
> > + if (pdx->sCurrentState == U14ERR_TIME)
> > + /* Do nothing if hardware in trouble */
> > return;
>
> Please wrap stuff like this in { } to not confuse people.
Yes please, or maybe put the comment on the return line like:
if (pdx->sCurrentState == U14ERR_TIME)
return; /* Do nothing if hardware in trouble */
or above the test like:
/* Do nothing if hardware in trouble */
if (pdx->sCurrentState == U14ERR_TIME)
return;
next prev parent reply other threads:[~2014-01-14 2:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-13 19:41 Pol Eyschen
2014-01-13 21:35 ` Mark Einon
2014-01-13 21:44 ` Dan Carpenter
2014-01-13 22:31 ` Pol Eyschen
2014-01-13 22:38 ` Dan Carpenter
2014-01-13 22:41 ` Greg KH
2014-01-13 23:56 ` Greg KH
2014-01-14 2:19 ` Joe Perches [this message]
2014-01-14 5:09 ` [PATCH] staging: ced1401: Fix dev_<level> messages Joe Perches
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=1389665978.24849.27.camel@joe-AO722 \
--to=joe@perches.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=jack@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=poleyschen@gmail.com \
--cc=poleyschen@hotmail.com \
--cc=sachin.kamat@linaro.org \
--cc=ufimtseva@gmail.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
all inboxes | Powered by JetHome®