From: Joe Eloff <kagen101@gmail.com>
To: Aldo Cedillo <aldobrett11@gmail.com>
Cc: gregkh@suse.de, mchehab@redhat.com, olimpiu.pascariu@gmail.com,
julia@diku.dk, tj@kernel.org, devel@driverdev.osuosl.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Staging: cx25821: fix brace coding style issue in cx25821-audio-upstream.c
Date: Tue, 06 Jul 2010 19:24:44 +0200 [thread overview]
Message-ID: <1278437084.5396.81.camel@dermezel> (raw)
In-Reply-To: <AANLkTil_Pu76aEje-5FP9nmxba--pmmAX3YkqNdzN3xX@mail.gmail.com>
On Tue, 2010-07-06 at 12:12 -0500, Aldo Cedillo wrote:
> > Subject: [PATCH] Staging: cx25821: fix brace coding style issue in cx25821-audio-upstream.c
> > This is a patch to the cx25821.c file that fixes up a brace warning found by the checkpatch.pl tool
> > Signed-off-by: Joe Eloff <kagen101@gmail.com>
> >
> > ---
> > drivers/staging/cx25821/cx25821-audio-upstream.c | 4 ++--
> > 1 files changed, 2 insertions(+), 2 deletions(-)
> >
> > diff --git a/drivers/staging/cx25821/cx25821-audio-upstream.c b/drivers/staging/cx25821/cx25821-audio-upstream.c
> > index eb39d13..e7346ec 100644
> > --- a/drivers/staging/cx25821/cx25821-audio-upstream.c
> > +++ b/drivers/staging/cx25821/cx25821-audio-upstream.c
> > @@ -762,9 +762,9 @@ int cx25821_audio_upstream_init(struct cx25821_dev *dev, int channel_select)
> > str_length + 1);
>
>
> I haven't tried checkpatch.pl over that file, but in the CodingStyle
> document you can read this:
>
> Do not unnecessarily use braces where a single statement will do.
>
> if (condition)
> action();
>
> This does not apply if one branch of a conditional statement is a single
> statement. Use braces in both branches.
>
> if (condition) {
> do_this();
> do_that();
> } else {
> otherwise();
> }
>
> Which one is the correct style? I ask these because I have seen this
> in other parts of the kernel. So maybe I can help to homogenize this.
>
> > /* Default if filename is empty string */
> > - if (strcmp(dev->input_audiofilename, "") == 0) {
> > + if (strcmp(dev->input_audiofilename, "") == 0)
> > dev->_audiofilename = "/root/audioGOOD.wav";
> > - }
> I believe only this one has to go.
> > +
> > } else {
> So the first brace closes the brace of the if line.
> > str_length = strlen(_defaultAudioName);
> > dev->_audiofilename = kmalloc(str_length + 1, GFP_KERNEL);
>
> Thanks,
> Aldo Brett
Thats good to know thanks for pointing that out, I have picked up a few
discrepancies with interpretation and checkpatch.pl.
Am noting it and trying to patch checkpatch.pl as I continue :).
I think checkpatch.pl points this out as the opposite to interpretation
thou otherwise I would not have patched it I guess.
Current TODO on checkpatch:
1. type i = 0 ; /* space before ; is not picked up by checkpatch.
2. What you mentioned is interpreted different by checkpatch.pl
Regards,
Joe
next prev parent reply other threads:[~2010-07-06 18:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-04 10:09 [PATCH] Staging: cx25821: fix brace coding style issue in cx25821-audio-upstream.c Joe Eloff
2010-07-06 17:12 ` Aldo Cedillo
2010-07-06 17:24 ` Joe Eloff [this message]
2010-07-06 17:37 ` Mauro Carvalho Chehab
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=1278437084.5396.81.camel@dermezel \
--to=kagen101@gmail.com \
--cc=aldobrett11@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@suse.de \
--cc=julia@diku.dk \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@redhat.com \
--cc=olimpiu.pascariu@gmail.com \
--cc=tj@kernel.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