From: kbuild test robot <lkp@intel.com>
To: Tony Lindgren <tony@atomide.com>
Cc: kbuild-all@01.org, Kishon Vijay Abraham I <kishon@ti.com>,
linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
linux-omap@vger.kernel.org, devicetree@vger.kernel.org,
Mark Rutland <mark.rutland@arm.com>,
Marcel Partap <mpartap@gmx.net>,
Michael Scott <michael.scott@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Sebastian Reichel <sre@kernel.org>
Subject: Re: [PATCH] phy: mapphone-mdm6600: Add USB PHY driver for MDM6600 on Droid 4
Date: Mon, 19 Feb 2018 15:45:38 +0800 [thread overview]
Message-ID: <201802191503.yJma6SYG%fengguang.wu@intel.com> (raw)
In-Reply-To: <20180217210723.7013-1-tony@atomide.com>
Hi Tony,
I love your patch! Perhaps something to improve:
[auto build test WARNING on phy/next]
[also build test WARNING on v4.16-rc2 next-20180216]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
url: https://github.com/0day-ci/linux/commits/Tony-Lindgren/phy-mapphone-mdm6600-Add-USB-PHY-driver-for-MDM6600-on-Droid-4/20180219-131127
base: https://git.kernel.org/pub/scm/linux/kernel/git/kishon/linux-phy.git next
reproduce:
# apt-get install sparse
make ARCH=x86_64 allmodconfig
make C=1 CF=-D__CHECK_ENDIAN__
sparse warnings: (new ones prefixed by >>)
>> drivers/phy/motorola/phy-mapphone-mdm6600.c:354:24: sparse: incompatible types for operation (>=)
drivers/phy/motorola/phy-mapphone-mdm6600.c:354:24: left side has type struct gpio_desc
drivers/phy/motorola/phy-mapphone-mdm6600.c:354:24: right side has type int
>> drivers/phy/motorola/phy-mapphone-mdm6600.c:354:24: sparse: incorrect type in conditional
drivers/phy/motorola/phy-mapphone-mdm6600.c:354:24: got bad type
vim +354 drivers/phy/motorola/phy-mapphone-mdm6600.c
340
341 /**
342 * phy_mdm6600_device_power_off() - power off mdm6600 device
343 * @ddata: device driver data
344 */
345 static void phy_mdm6600_device_power_off(struct phy_mdm6600 *ddata)
346 {
347 struct gpio_desc *reset_gpio =
348 ddata->gpio[PHY_MDM6600_RESET];
349
350 ddata->enabled = false;
351 phy_mdm6600_cmd(ddata, AP_STATUS_BP_SHUTDOWN_REQ);
352 msleep(100);
353
> 354 if (reset_gpio >= 0)
355 gpiod_set_value_cansleep(reset_gpio, 1);
356
357 dev_info(ddata->dev, "Waiting for power down request to complete.. ");
358 if (wait_for_completion_timeout(&ddata->ack,
359 msecs_to_jiffies(5000))) {
360 dev_info(ddata->dev, "Powered down OK\n");
361 } else {
362 dev_err(ddata->dev, "Timed out powering down\n");
363 }
364 }
365
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
next prev parent reply other threads:[~2018-02-19 7:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-17 21:07 Tony Lindgren
2018-02-18 0:31 ` Sebastian Reichel
2018-02-18 17:50 ` Tony Lindgren
2018-02-19 7:45 ` kbuild test robot [this message]
2018-03-01 3:47 ` Tony Lindgren
2018-02-19 20:40 ` Rob Herring
2018-03-01 3:46 ` Tony Lindgren
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=201802191503.yJma6SYG%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=devicetree@vger.kernel.org \
--cc=kbuild-all@01.org \
--cc=kishon@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=michael.scott@linaro.org \
--cc=mpartap@gmx.net \
--cc=robh+dt@kernel.org \
--cc=sre@kernel.org \
--cc=tony@atomide.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
all inboxes | Powered by JetHome®