From: kbuild test robot <lkp@intel.com>
To: "Andrew F. Davis" <afd@ti.com>
Cc: kbuild-all@01.org, Rob Herring <robh+dt@kernel.org>,
Pawel Moll <pawel.moll@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Kumar Gala <galak@codeaurora.org>,
Lee Jones <lee.jones@linaro.org>, Mark Brown <broonie@kernel.org>,
Alexandre Courbot <gnurou@gmail.com>,
Grygorii Strashko <grygorii.strashko@ti.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
"Andrew F. Davis" <afd@ti.com>
Subject: Re: [PATCH v4 3/5] mfd: tps65912: Add driver for the TPS65912 PMIC
Date: Fri, 2 Oct 2015 04:57:21 +0800 [thread overview]
Message-ID: <201510020454.0apm0UhS%fengguang.wu@intel.com> (raw)
In-Reply-To: <1443731874-21362-4-git-send-email-afd@ti.com>
[-- Attachment #1: Type: text/plain, Size: 6709 bytes --]
Hi Andrew,
[auto build test results on v4.3-rc3 -- if it's inappropriate base, please ignore]
config: tile-allyesconfig (attached as .config)
reproduce:
wget https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
git checkout d617dea974adf7dc262f2d49dea24a673e0403e2
# save the attached .config to linux build tree
make.cross ARCH=tile
All warnings (new ones prefixed by >>):
drivers/mfd/tps65912-core.c:29:2: error: implicit declaration of function 'REGMAP_IRQ_REG'
drivers/mfd/tps65912-core.c:29:2: warning: missing braces around initializer
>> drivers/mfd/tps65912-core.c:29:2: warning: (near initialization for
drivers/mfd/tps65912-core.c:29:2: error: initializer element is not constant
drivers/mfd/tps65912-core.c:29:2: error: (near initialization for
drivers/mfd/tps65912-core.c:30:2: error: initializer element is not constant
drivers/mfd/tps65912-core.c:30:2: error: (near initialization for
drivers/mfd/tps65912-core.c:31:2: error: initializer element is not constant
drivers/mfd/tps65912-core.c:31:2: error: (near initialization for
drivers/mfd/tps65912-core.c:32:2: error: initializer element is not constant
drivers/mfd/tps65912-core.c:32:2: error: (near initialization for
drivers/mfd/tps65912-core.c:33:2: error: initializer element is not constant
drivers/mfd/tps65912-core.c:33:2: error: (near initialization for
drivers/mfd/tps65912-core.c:34:2: error: initializer element is not constant
drivers/mfd/tps65912-core.c:34:2: error: (near initialization for
drivers/mfd/tps65912-core.c:35:2: error: initializer element is not constant
drivers/mfd/tps65912-core.c:35:2: error: (near initialization for
drivers/mfd/tps65912-core.c:36:2: error: initializer element is not constant
drivers/mfd/tps65912-core.c:36:2: error: (near initialization for
drivers/mfd/tps65912-core.c:38:2: error: initializer element is not constant
drivers/mfd/tps65912-core.c:38:2: error: (near initialization for
drivers/mfd/tps65912-core.c:39:2: error: initializer element is not constant
drivers/mfd/tps65912-core.c:39:2: error: (near initialization for
drivers/mfd/tps65912-core.c:40:2: error: initializer element is not constant
drivers/mfd/tps65912-core.c:40:2: error: (near initialization for
drivers/mfd/tps65912-core.c:41:2: error: initializer element is not constant
drivers/mfd/tps65912-core.c:41:2: error: (near initialization for
drivers/mfd/tps65912-core.c:42:2: error: initializer element is not constant
drivers/mfd/tps65912-core.c:42:2: error: (near initialization for
drivers/mfd/tps65912-core.c:43:2: error: initializer element is not constant
drivers/mfd/tps65912-core.c:43:2: error: (near initialization for
drivers/mfd/tps65912-core.c:44:2: error: initializer element is not constant
drivers/mfd/tps65912-core.c:44:2: error: (near initialization for
drivers/mfd/tps65912-core.c:45:2: error: initializer element is not constant
drivers/mfd/tps65912-core.c:45:2: error: (near initialization for
drivers/mfd/tps65912-core.c:47:2: error: initializer element is not constant
drivers/mfd/tps65912-core.c:47:2: error: (near initialization for
drivers/mfd/tps65912-core.c:48:2: error: initializer element is not constant
drivers/mfd/tps65912-core.c:48:2: error: (near initialization for
drivers/mfd/tps65912-core.c:49:2: error: initializer element is not constant
drivers/mfd/tps65912-core.c:49:2: error: (near initialization for
drivers/mfd/tps65912-core.c:50:2: error: initializer element is not constant
drivers/mfd/tps65912-core.c:50:2: error: (near initialization for
drivers/mfd/tps65912-core.c:51:2: error: initializer element is not constant
drivers/mfd/tps65912-core.c:51:2: error: (near initialization for
drivers/mfd/tps65912-core.c:52:2: error: initializer element is not constant
drivers/mfd/tps65912-core.c:52:2: error: (near initialization for
drivers/mfd/tps65912-core.c:53:2: error: initializer element is not constant
drivers/mfd/tps65912-core.c:53:2: error: (near initialization for
drivers/mfd/tps65912-core.c:54:2: error: initializer element is not constant
drivers/mfd/tps65912-core.c:54:2: error: (near initialization for
drivers/mfd/tps65912-core.c:56:2: error: initializer element is not constant
drivers/mfd/tps65912-core.c:56:2: error: (near initialization for
drivers/mfd/tps65912-core.c:57:2: error: initializer element is not constant
drivers/mfd/tps65912-core.c:57:2: error: (near initialization for
drivers/mfd/tps65912-core.c:58:2: error: initializer element is not constant
drivers/mfd/tps65912-core.c:58:2: error: (near initialization for
drivers/mfd/tps65912-core.c:59:2: error: initializer element is not constant
drivers/mfd/tps65912-core.c:59:2: error: (near initialization for
drivers/mfd/tps65912-core.c:60:2: error: initializer element is not constant
drivers/mfd/tps65912-core.c:60:2: error: (near initialization for
drivers/mfd/tps65912-core.c:61:2: error: initializer element is not constant
drivers/mfd/tps65912-core.c:61:2: error: (near initialization for
cc1: some warnings being treated as errors
vim +29 drivers/mfd/tps65912-core.c
13 * kind, whether expressed or implied; without even the implied warranty
14 * of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
15 * GNU General Public License version 2 for more details.
16 *
17 * Based on the TPS65218 driver and the previous TPS65912 driver by
18 * Margarita Olaya Cabrera <magi@slimlogic.co.uk>
19 */
20
21 #include <linux/interrupt.h>
22 #include <linux/module.h>
23 #include <linux/of_device.h>
24
25 #include <linux/mfd/tps65912.h>
26
27 static const struct regmap_irq tps65912_irqs[] = {
28 /* INT_STS IRQs */
> 29 REGMAP_IRQ_REG(TPS65912_IRQ_PWRHOLD_F, 0, TPS65912_INT_STS_PWRHOLD_F),
30 REGMAP_IRQ_REG(TPS65912_IRQ_VMON, 0, TPS65912_INT_STS_VMON),
31 REGMAP_IRQ_REG(TPS65912_IRQ_PWRON, 0, TPS65912_INT_STS_PWRON),
32 REGMAP_IRQ_REG(TPS65912_IRQ_PWRON_LP, 0, TPS65912_INT_STS_PWRON_LP),
33 REGMAP_IRQ_REG(TPS65912_IRQ_PWRHOLD_R, 0, TPS65912_INT_STS_PWRHOLD_R),
34 REGMAP_IRQ_REG(TPS65912_IRQ_HOTDIE, 0, TPS65912_INT_STS_HOTDIE),
35 REGMAP_IRQ_REG(TPS65912_IRQ_GPIO1_R, 0, TPS65912_INT_STS_GPIO1_R),
36 REGMAP_IRQ_REG(TPS65912_IRQ_GPIO1_F, 0, TPS65912_INT_STS_GPIO1_F),
37 /* INT_STS2 IRQs */
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/octet-stream, Size: 41634 bytes --]
next prev parent reply other threads:[~2015-10-01 20:58 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-01 20:37 [PATCH v4 0/5] mfd: tps65912: Driver rewrite with DT support Andrew F. Davis
2015-10-01 20:37 ` [PATCH v4 1/5] Documentation: tps65912: Add DT bindings for the TPS65912 PMIC Andrew F. Davis
2015-10-01 20:37 ` [PATCH v4 2/5] mfd: tps65912: Remove old driver in preparation for new driver Andrew F. Davis
2015-10-05 9:28 ` Lee Jones
2015-10-05 9:29 ` Lee Jones
2015-10-05 16:01 ` Andrew F. Davis
2015-10-01 20:37 ` [PATCH v4 3/5] mfd: tps65912: Add driver for the TPS65912 PMIC Andrew F. Davis
2015-10-01 20:51 ` kbuild test robot
[not found] ` <20151002095859.GN12635@sirena.org.uk>
2015-10-02 13:32 ` [lkp] " Fengguang Wu
2015-10-02 13:47 ` Mark Brown
2015-10-01 20:57 ` kbuild test robot [this message]
2015-10-01 20:57 ` kbuild test robot
2015-10-01 23:49 ` Andrew F. Davis
2015-10-05 9:24 ` Lee Jones
2015-10-05 9:27 ` Lee Jones
2015-10-12 15:06 ` Andrew F. Davis
2015-10-13 7:34 ` Lee Jones
2015-10-01 20:37 ` [PATCH v4 4/5] regulator: tps65912: Add regulator " Andrew F. Davis
2015-10-02 19:21 ` Grygorii Strashko
2015-10-22 16:47 ` Mark Brown
2015-10-23 12:46 ` Andrew F. Davis
2015-10-23 23:18 ` Mark Brown
2015-10-24 0:11 ` Andrew F. Davis
2015-10-24 22:14 ` Mark Brown
2015-10-25 20:45 ` Andrew F. Davis
2015-10-26 0:43 ` Mark Brown
2015-10-26 15:47 ` Andrew F. Davis
2015-10-27 0:16 ` Mark Brown
2015-10-27 14:23 ` Andrew F. Davis
2015-11-04 15:35 ` Andrew F. Davis
2015-11-05 10:14 ` Mark Brown
2015-11-05 18:04 ` Andrew F. Davis
2015-11-06 10:43 ` Mark Brown
2015-11-06 18:10 ` Andrew F. Davis
2015-11-06 21:16 ` Mark Brown
2015-11-09 17:41 ` Andrew F. Davis
2015-11-10 9:57 ` Mark Brown
2015-11-10 16:47 ` Andrew F. Davis
2015-11-10 17:04 ` Mark Brown
2015-11-10 17:52 ` Andrew F. Davis
2015-11-10 18:44 ` Mark Brown
2015-11-10 19:40 ` Andrew F. Davis
2015-11-16 18:23 ` Mark Brown
2015-10-01 20:37 ` [PATCH v4 5/5] gpio: tps65912: Add GPIO " Andrew F. Davis
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=201510020454.0apm0UhS%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=afd@ti.com \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=gnurou@gmail.com \
--cc=grygorii.strashko@ti.com \
--cc=ijc+devicetree@hellion.org.uk \
--cc=kbuild-all@01.org \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@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®