From: kbuild test robot <lkp@intel.com>
Cc: kbuild-all@01.org, linux-arm-msm@vger.kernel.org,
linux-kernel@vger.kernel.org,
Thierry Reding <thierry.reding@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
linux-pwm@vger.kernel.org, devicetree@vger.kernel.org,
subbaram@quicinc.com, aghayal@qti.qualcomm.com,
wruan@quicinc.com, kgunda@qti.qualcomm.com,
Fenglin Wu <fenglinw@codeaurora.org>
Subject: Re: [PATCH V1 2/2] pwm: pwm-qti-lpg: Add PWM driver for QTI LPG module
Date: Sun, 4 Jun 2017 07:20:29 +0800 [thread overview]
Message-ID: <201706040741.cENZvRyX%fengguang.wu@intel.com> (raw)
In-Reply-To: <20170531061541.10808-3-fenglinw@codeaurora.org>
[-- Attachment #1: Type: text/plain, Size: 2055 bytes --]
Hi Fenglin,
[auto build test ERROR on j.anaszewski-leds/for-next]
[also build test ERROR on v4.12-rc3 next-20170602]
[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/fenglinw-codeaurora-org/leds-leds-qti-rgb-Add-LED-driver-for-QTI-TRI_LED-module/20170531-153634
base: https://git.kernel.org/pub/scm/linux/kernel/git/j.anaszewski/linux-leds.git for-next
config: m68k-allyesconfig (attached as .config)
compiler: m68k-linux-gcc (GCC) 4.9.0
reproduce:
wget https://raw.githubusercontent.com/01org/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# save the attached .config to linux build tree
make.cross ARCH=m68k
All errors (new ones prefixed by >>):
drivers/pwm/pwm-qti-lpg.c: In function 'qti_lpg_pwm_dbg_show':
>> drivers/pwm/pwm-qti-lpg.c:428:4: error: implicit declaration of function 'seq_printf' [-Werror=implicit-function-declaration]
seq_printf(s, "LPG %d is requested by %s\n",
^
>> drivers/pwm/pwm-qti-lpg.c:437:4: error: implicit declaration of function 'seq_puts' [-Werror=implicit-function-declaration]
seq_puts(s, " enabled\n");
^
cc1: some warnings being treated as errors
vim +/seq_printf +428 drivers/pwm/pwm-qti-lpg.c
422 if (lpg == NULL) {
423 dev_err(pwm_chip->dev, "lpg not found\n");
424 return;
425 }
426
427 if (test_bit(PWMF_REQUESTED, &pwm->flags)) {
> 428 seq_printf(s, "LPG %d is requested by %s\n",
429 lpg->lpg_idx + 1, pwm->label);
430 } else {
431 seq_printf(s, "LPG %d is free\n",
432 lpg->lpg_idx + 1);
433 continue;
434 }
435
436 if (pwm_is_enabled(pwm)) {
> 437 seq_puts(s, " enabled\n");
438 } else {
439 seq_puts(s, " disabled\n");
440 continue;
---
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: 41150 bytes --]
next prev parent reply other threads:[~2017-06-03 23:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20170531061541.10808-1-fenglinw@codeaurora.org>
2017-05-31 6:14 ` [PATCH V1 2/2] pwm: pwm-qti-lpg: Add PWM driver for QTI LPG module fenglinw
2017-06-03 23:20 ` kbuild test robot [this message]
2017-06-07 21:19 ` Rob Herring
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=201706040741.cENZvRyX%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=aghayal@qti.qualcomm.com \
--cc=devicetree@vger.kernel.org \
--cc=fenglinw@codeaurora.org \
--cc=kbuild-all@01.org \
--cc=kgunda@qti.qualcomm.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=subbaram@quicinc.com \
--cc=thierry.reding@gmail.com \
--cc=wruan@quicinc.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