From: Dan Murphy <dmurphy@ti.com>
To: Dan Carpenter <dan.carpenter@oracle.com>, <kbuild@lists.01.org>,
<sre@kernel.org>
Cc: <lkp@intel.com>, <kbuild-all@lists.01.org>,
<linux-pm@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<devicetree@vger.kernel.org>, <robh@kernel.org>,
Ricardo Rivera-Matos <r-rivera-matos@ti.com>
Subject: Re: [PATCH v3 2/2] power: supply: bq25790: Introduce the BQ25790 charger driver
Date: Fri, 9 Oct 2020 07:18:20 -0500 [thread overview]
Message-ID: <a38c3dcd-4e19-0d99-105c-c2cb0a645eb6@ti.com> (raw)
In-Reply-To: <20201009121532.GN1042@kadam>
Dan
On 10/9/20 7:15 AM, Dan Carpenter wrote:
> Hi Dan,
>
> url: https://github.com/0day-ci/linux/commits/Dan-Murphy/dt-bindings-power-Add-the-bq25790-dt-bindings/20201008-234450
> base: https://git.kernel.org/pub/scm/linux/kernel/git/sre/linux-power-supply.git for-next
> config: i386-randconfig-m021-20201009 (attached as .config)
> compiler: gcc-9 (Debian 9.3.0-15) 9.3.0
>
> If you fix the issue, kindly add following tag as appropriate
> Reported-by: kernel test robot <lkp@intel.com>
> Reported-by: Dan Carpenter <dan.carpenter@oracle.com>
>
> smatch warnings:
> drivers/power/supply/bq25790_charger.c:170 bq25790_usb_work() warn: ignoring unreachable code.
> drivers/power/supply/bq25790_charger.c:624 bq25790_get_property() warn: should this be a bitwise op?
Fixing both of these now
Dan
prev parent reply other threads:[~2020-10-09 12:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-08 15:43 [PATCH v3 1/2] dt-bindings: power: Add the bq25790 dt bindings Dan Murphy
2020-10-08 15:43 ` [PATCH v3 2/2] power: supply: bq25790: Introduce the BQ25790 charger driver Dan Murphy
2020-10-09 0:51 ` kernel test robot
2020-10-09 12:15 ` Dan Carpenter
2020-10-09 12:18 ` Dan Murphy [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=a38c3dcd-4e19-0d99-105c-c2cb0a645eb6@ti.com \
--to=dmurphy@ti.com \
--cc=dan.carpenter@oracle.com \
--cc=devicetree@vger.kernel.org \
--cc=kbuild-all@lists.01.org \
--cc=kbuild@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=lkp@intel.com \
--cc=r-rivera-matos@ti.com \
--cc=robh@kernel.org \
--cc=sre@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;
as well as URLs for NNTP newsgroup(s).