From: kbuild test robot <lkp@intel.com>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: kbuild-all@01.org, Thierry Reding <thierry.reding@gmail.com>,
devel@driverdev.osuosl.org, linux-pwm@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Johan Hovold <johan@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] pwm: Remove pwm_can_sleep()
Date: Wed, 4 Jan 2017 23:20:23 +0800 [thread overview]
Message-ID: <201701042316.vJFInyKO%fengguang.wu@intel.com> (raw)
In-Reply-To: <20170104091348.31277-1-thierry.reding@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2107 bytes --]
Hi Thierry,
[auto build test ERROR on pwm/for-next]
[also build test ERROR on v4.10-rc2 next-20170104]
[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/Thierry-Reding/pwm-Remove-pwm_can_sleep/20170104-222234
base: https://git.kernel.org/pub/scm/linux/kernel/git/thierry.reding/linux-pwm.git for-next
config: x86_64-randconfig-i0-201701 (attached as .config)
compiler: gcc-4.9 (Debian 4.9.4-2) 4.9.4
reproduce:
# save the attached .config to linux build tree
make ARCH=x86_64
All errors (new ones prefixed by >>):
drivers/leds/leds-pwm.c: In function 'led_pwm_add':
>> drivers/leds/leds-pwm.c:115:2: error: implicit declaration of function 'pwm_can_sleep' [-Werror=implicit-function-declaration]
led_data->can_sleep = pwm_can_sleep(led_data->pwm);
^
cc1: some warnings being treated as errors
vim +/pwm_can_sleep +115 drivers/leds/leds-pwm.c
5f7b03dc Russell King 2014-04-06 109 ret = PTR_ERR(led_data->pwm);
5f7b03dc Russell King 2014-04-06 110 dev_err(dev, "unable to request PWM for %s: %d\n",
5f7b03dc Russell King 2014-04-06 111 led->name, ret);
5f7b03dc Russell King 2014-04-06 112 return ret;
5f7b03dc Russell King 2014-04-06 113 }
5f7b03dc Russell King 2014-04-06 114
5f7b03dc Russell King 2014-04-06 @115 led_data->can_sleep = pwm_can_sleep(led_data->pwm);
9aa07625 Jacek Anaszewski 2015-08-20 116 if (!led_data->can_sleep)
9aa07625 Jacek Anaszewski 2015-08-20 117 led_data->cdev.brightness_set = led_pwm_set;
9aa07625 Jacek Anaszewski 2015-08-20 118 else
:::::: The code at line 115 was first introduced by commit
:::::: 5f7b03dc2ab5f4ca16e5d6bc3e6dcd2953c6fede leds: leds-pwm: provide a common function to setup a single led-pwm device
:::::: TO: Russell King <rmk+kernel@arm.linux.org.uk>
:::::: CC: Bryan Wu <cooloney@gmail.com>
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 24644 bytes --]
prev parent reply other threads:[~2017-01-04 15:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-04 9:13 [PATCH 1/2] pwm: Remove pwm_can_sleep() Thierry Reding
2017-01-04 9:13 ` [PATCH 2/2] pwm: Remove .can_sleep from struct pwm_chip Thierry Reding
2017-01-04 15:20 ` kbuild test robot [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=201701042316.vJFInyKO%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=johan@kernel.org \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=thierry.reding@gmail.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).