From: Joe Perches <joe@perches.com>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: Martin Kepplinger <martink@posteo.de>,
gregkh@linuxfoundation.org, devel@driverdev.osuosl.org,
linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
m.chehab@samsung.com
Subject: Re: [PATCHv2] staging: media: as102: replace custom dprintk() with dev_dbg()
Date: Mon, 04 Aug 2014 04:12:12 -0700 [thread overview]
Message-ID: <1407150732.16152.59.camel@joe-AO725> (raw)
In-Reply-To: <20140804104016.GQ4804@mwanda>
On Mon, 2014-08-04 at 13:40 +0300, Dan Carpenter wrote:
> On Mon, Aug 04, 2014 at 12:17:14PM +0200, Martin Kepplinger wrote:
[]
> > + if (dev) {
> > + dev_dbg(&dev->bus_adap.usb_dev->dev,
> > + "tuner parameters: freq: %d bw: 0x%02x gi: 0x%02x\n",
> > + params->frequency,
> > + tune_args->bandwidth,
> > + tune_args->guard_interval);
> > + } else {
> > + pr_debug("as102: tuner parameters: freq: %d bw: 0x%02x gi: 0x%02x\n",
> > params->frequency,
> > tune_args->bandwidth,
> > tune_args->guard_interval);
> > + }
[]
> This isn't indented correctly. I wish checkpatch.pl would catch that...
> Anyway, the else side can be removed as explained earlier.
checkpatch doesn't warn on any of:
$ cat t.c
static int func(void **bar)
{
bool b;
/* test */
int a[2] = {
3,
6
};
if (b) {
b = a[0] == a[1];
}
return a[b];
}
$
I think it'd be better if it would one day
but it doesn't seem as simple as it seems
for checkpatch to do it.
next prev parent reply other threads:[~2014-08-04 11:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-03 14:54 [PATCH] staging: media: as102: replace custom dprintk() with dev_dbg() Martin Kepplinger
2014-08-04 9:10 ` Dan Carpenter
2014-08-04 10:17 ` [PATCHv2] " Martin Kepplinger
2014-08-04 10:40 ` Dan Carpenter
2014-08-04 11:12 ` Joe Perches [this message]
2014-08-04 11:13 ` [PATCHv3] " Martin Kepplinger
-- strict thread matches above, loose matches on Subject: below --
2014-05-17 13:59 [PATCH] " Antti Palosaari
2014-05-17 16:05 ` [PATCHv2] " Martin Kepplinger
2014-05-17 17:21 ` Antti Palosaari
2014-05-17 17:52 ` Martin Kepplinger
2014-05-17 18:43 ` Gianluca Gennari
2014-05-17 19:22 ` Dan Carpenter
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=1407150732.16152.59.camel@joe-AO725 \
--to=joe@perches.com \
--cc=dan.carpenter@oracle.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=m.chehab@samsung.com \
--cc=martink@posteo.de \
/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