From: kbuild test robot <lkp@intel.com>
To: Bhushan Shah <bshah@kde.org>
Cc: kbuild-all@01.org, Lee Jones <lee.jones@linaro.org>,
Daniel Thompson <daniel.thompson@linaro.org>,
Jingoo Han <jingoohan1@gmail.com>,
Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>,
linux-fbdev@vger.kernel.org, linux-kernel@vger.kernel.org,
Bhushan Shah <bshah@kde.org>
Subject: Re: [PATCH] backlight: lm3630a: bump REG_MAX value to 0x50 instead of 0x1F
Date: Thu, 22 Jun 2017 08:46:57 +0800 [thread overview]
Message-ID: <201706220825.WnSVl1Fq%fengguang.wu@intel.com> (raw)
In-Reply-To: <20170621052450.2258-1-bshah@kde.org>
[-- Attachment #1: Type: text/plain, Size: 1558 bytes --]
Hi Bhushan,
[auto build test ERROR on v4.12-rc6]
[also build test ERROR on next-20170621]
[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/Bhushan-Shah/backlight-lm3630a-bump-REG_MAX-value-to-0x50-instead-of-0x1F/20170622-074946
config: i386-randconfig-x011-06190614 (attached as .config)
compiler: gcc-6 (Debian 6.2.0-3) 6.2.0 20160901
reproduce:
# save the attached .config to linux build tree
make ARCH=i386
All errors (new ones prefixed by >>):
drivers/video/backlight/lm3630a_bl.c: In function 'lm3630a_chip_init':
>> drivers/video/backlight/lm3630a_bl.c:84:30: error: 'FLTR_STR' undeclared (first use in this function)
rval = lm3630a_write(pchip, FLTR_STR, 0x03);
^~~~~~~~
drivers/video/backlight/lm3630a_bl.c:84:30: note: each undeclared identifier is reported only once for each function it appears in
vim +/FLTR_STR +84 drivers/video/backlight/lm3630a_bl.c
78 {
79 int rval;
80 struct lm3630a_platform_data *pdata = pchip->pdata;
81
82 usleep_range(1000, 2000);
83 /* set Filter Strength Register */
> 84 rval = lm3630a_write(pchip, FLTR_STR, 0x03);
85 /* set Cofig. register */
86 rval |= lm3630a_update(pchip, REG_CONFIG, 0x07, pdata->pwm_ctrl);
87 /* set boost control */
---
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: 22990 bytes --]
prev parent reply other threads:[~2017-06-22 0:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-21 5:24 Bhushan Shah
2017-06-21 5:31 ` [PATCH v2] " Bhushan Shah
2017-06-21 9:37 ` Daniel Thompson
2017-06-21 10:52 ` Bhushan Shah
2017-06-21 11:03 ` Daniel Thompson
2017-06-22 0:46 ` 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=201706220825.WnSVl1Fq%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=b.zolnierkie@samsung.com \
--cc=bshah@kde.org \
--cc=daniel.thompson@linaro.org \
--cc=jingoohan1@gmail.com \
--cc=kbuild-all@01.org \
--cc=lee.jones@linaro.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@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 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®