From: Dan Carpenter <dan.carpenter@oracle.com>
To: Krzysztof Kozlowski <k.kozlowski@samsung.com>
Cc: linux-input@vger.kernel.org
Subject: Re: power_supply: Change ownership from driver to core
Date: Mon, 23 Mar 2015 19:38:12 +0300 [thread overview]
Message-ID: <20150323163812.GL10964@mwanda> (raw)
In-Reply-To: <1427124108.30970.1.camel@AMDC1943>
On Mon, Mar 23, 2015 at 04:21:48PM +0100, Krzysztof Kozlowski wrote:
> On pon, 2015-03-23 at 17:54 +0300, Dan Carpenter wrote:
> > Hello Krzysztof Kozlowski,
> >
> > The patch 297d716f6260: "power_supply: Change ownership from driver
> > to core" from Mar 12, 2015, leads to the following static checker
> > warning:
> >
> > drivers/hid/hid-input.c:457 hidinput_setup_battery()
> > error: potential NULL dereference 'dev->battery'.
> >
>
> Yes, indeed. I'll fix it.
>
> I suppose Smatch detected this so I wonder why it does not print this
> warning in my configuration (I tried v0.5.0-2916-gbdbeaee0221e and
> v0.5.0-3008-g08de8666209d
That check in the released code buggy is buggy so it doesn't print many
warnings. When I fixed it, then it prints warnings which look like
real bugs but are false positives. I'm debating if I should just delete
the check.
Also I was just about to email about this one.
drivers/power/charger-manager.c:1775 charger_manager_probe()
error: 'cm->charger_psy' dereferencing possible ERR_PTR()
drivers/power/charger-manager.c
1770
1771 cm->charger_psy = power_supply_register(NULL, &cm->charger_psy_desc,
1772 &psy_cfg);
1773 if (IS_ERR(cm->charger_psy)) {
1774 dev_err(&pdev->dev, "Cannot register charger-manager with name \"%s\"\n",
1775 cm->charger_psy->desc->name);
^^^^^^^^^^^^^^^
1776 return PTR_ERR(cm->charger_psy);
1777 }
1778
regards,
dan carpenter
prev parent reply other threads:[~2015-03-23 16:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-23 14:54 power_supply: Change ownership from driver to core Dan Carpenter
2015-03-23 15:21 ` Krzysztof Kozlowski
2015-03-23 16:38 ` Dan Carpenter [this message]
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=20150323163812.GL10964@mwanda \
--to=dan.carpenter@oracle.com \
--cc=k.kozlowski@samsung.com \
--cc=linux-input@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.