From: Pavel Machek <pavel@ucw.cz>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: ncase@xes-inc.com, linux-leds@vger.kernel.org
Subject: Re: [bug report] leds: Add support for Philips PCA955x I2C LED drivers
Date: Thu, 17 Aug 2017 15:27:40 +0200 [thread overview]
Message-ID: <20170817132740.GA20401@amd> (raw)
In-Reply-To: <20170817114835.ypyhfhurntb4egvx@mwanda>
[-- Attachment #1: Type: text/plain, Size: 1890 bytes --]
On Thu 2017-08-17 14:51:48, Dan Carpenter wrote:
> On Thu, Aug 17, 2017 at 01:27:38PM +0200, Pavel Machek wrote:
> > Hi!
> >
> > > Hello Nate Case,
> > >
> > > The patch f46e9203d9a1: "leds: Add support for Philips PCA955x I2C
> > > LED drivers" from Jul 16, 2008, leads to the following static checker
> > > warning:
> > > 472 /*
> > > 473 * Platform data can specify LED names and
> > > 474 * default triggers
> > > 475 */
> > > 476 if (pdata->leds[i].name)
> > > ^^^^^^^^^^^^^^^^^^^
> > > The comment implies that we should be testing pdata->leds[i].name[0] to
> > > see if any string has been set?
> >
> > Someone was already submitting patch from this one, no?
> >
> > And please don't mark this one as a "bug report". There's no bug. Your
> > code analysis tool found a way to make kernel code shorter... well, so
> > what?
> >
>
> You didn't read my email. It was only one sentence long... :/
I read your subject, and it claimed bug.
Bug normally means: Hey, there's problem with the driver. It oopses my
kernel here.
> >From the comments, it looked like maybe a different test was intended.
> Anyway, that's the point of these warnings is because many times the
> bogus NULL test should be replaced with a correct test. I don't forward
> the warning if it's obvious that the test should just be deleted.
>
> I probably could review the warnings even more but I am pretty busy and
> the code is obviously bogus and it's easier for the author.
Anyway, there was patch on the lists, already...
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2017-08-17 13:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-17 10:28 [bug report] leds: Add support for Philips PCA955x I2C LED drivers Dan Carpenter
2017-08-17 11:27 ` Pavel Machek
2017-08-17 11:51 ` Dan Carpenter
2017-08-17 13:27 ` Pavel Machek [this message]
2017-08-17 13:37 ` Dan Carpenter
2017-08-17 13:43 ` Dan Carpenter
2017-08-17 13:49 ` Dan Carpenter
2017-08-17 13:58 ` Pavel Machek
2017-08-17 13:58 ` Nate Case
2017-08-17 14:01 ` Dan Carpenter
2017-08-17 11:28 ` Pavel Machek
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=20170817132740.GA20401@amd \
--to=pavel@ucw.cz \
--cc=dan.carpenter@oracle.com \
--cc=linux-leds@vger.kernel.org \
--cc=ncase@xes-inc.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;
as well as URLs for NNTP newsgroup(s).