From: Lee Jones <lee.jones@linaro.org>
To: Laxman Dewangan <ldewangan@nvidia.com>
Cc: kbuild test robot <lkp@intel.com>,
kbuild-all@01.org, robh+dt@kernel.org, pawel.moll@arm.com,
mark.rutland@arm.com, ijc+devicetree@hellion.org.uk,
galak@codeaurora.org, linus.walleij@linaro.org, gnurou@gmail.com,
broonie@kernel.org, a.zummo@towertech.it,
alexandre.belloni@free-electrons.com, lgirdwood@gmail.com,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-gpio@vger.kernel.org, rtc-linux@googlegroups.com,
swarren@nvidia.com, treding@nvidia.com, k.kozlowski@samsung.com,
vreddytalla@nvidia.com, Mallikarjun Kasoju <mkasoju@nvidia.com>
Subject: Re: [PATCH V7 2/8] mfd: max77620: add core driver for MAX77620/MAX20024
Date: Mon, 1 Feb 2016 08:25:53 +0000 [thread overview]
Message-ID: <20160201082553.GW3368@x1> (raw)
In-Reply-To: <56ACEEE1.1050800@nvidia.com>
On Sat, 30 Jan 2016, Laxman Dewangan wrote:
> This depends on patch
> [PATCH V2] mfd: core: add macro for adding mfd cells
>
> and due to absence of this patch, it reports the error.
If you have dependencies, why aren't they in this set?
> On Saturday 30 January 2016 10:46 PM, kbuild test robot wrote:
> >Hi Laxman,
> >
> >[auto build test ERROR on pinctrl/for-next]
> >[also build test ERROR on v4.5-rc1 next-20160129]
> >[if your patch is applied to the wrong git tree, please drop us a note to help improving the system]
> >
> >url: https://github.com/0day-ci/linux/commits/Laxman-Dewangan/Add-support-for-MAXIM-MAX77620-MAX20024-PMIC/20160131-005355
> >base: https://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-pinctrl.git for-next
> >config: i386-allmodconfig (attached as .config)
> >reproduce:
> > # save the attached .config to linux build tree
> > make ARCH=i386
> >
> >All errors (new ones prefixed by >>):
> >
> >>>drivers/mfd/max77620.c:57:2: error: implicit declaration of function 'DEFINE_MFD_CELL_NAME' [-Werror=implicit-function-declaration]
> > DEFINE_MFD_CELL_NAME("max77620-pinctrl"),
> > ^
> >>>drivers/mfd/max77620.c:57:2: error: initializer element is not constant
> > drivers/mfd/max77620.c:57:2: note: (near initialization for 'max77620_children[0].name')
> >>>drivers/mfd/max77620.c:58:2: error: implicit declaration of function 'DEFINE_MFD_CELL_NAME_RESOURCE' [-Werror=implicit-function-declaration]
> > DEFINE_MFD_CELL_NAME_RESOURCE("max77620-gpio", gpio_resources),
> > ^
> > drivers/mfd/max77620.c:58:2: error: initializer element is not constant
> > drivers/mfd/max77620.c:58:2: note: (near initialization for 'max77620_children[0].id')
> > drivers/mfd/max77620.c:59:2: error: initializer element is not constant
> > DEFINE_MFD_CELL_NAME("max77620-pmic"),
> > ^
> > drivers/mfd/max77620.c:59:2: note: (near initialization for 'max77620_children[0].usage_count')
> > drivers/mfd/max77620.c:60:2: error: initializer element is not constant
> > DEFINE_MFD_CELL_NAME_RESOURCE("max77620-rtc", rtc_resources),
> > ^
> > drivers/mfd/max77620.c:60:2: note: (near initialization for 'max77620_children[0].enable')
> > drivers/mfd/max77620.c:61:2: error: initializer element is not constant
> > DEFINE_MFD_CELL_NAME_RESOURCE("max77620-power", power_resources),
> > ^
> > drivers/mfd/max77620.c:61:2: note: (near initialization for 'max77620_children[0].disable')
> > drivers/mfd/max77620.c:62:2: error: initializer element is not constant
> > DEFINE_MFD_CELL_NAME("max77620-watchdog"),
> > ^
> > drivers/mfd/max77620.c:62:2: note: (near initialization for 'max77620_children[0].suspend')
> > drivers/mfd/max77620.c:63:2: error: initializer element is not constant
> > DEFINE_MFD_CELL_NAME("max77620-clock"),
> > ^
> > drivers/mfd/max77620.c:63:2: note: (near initialization for 'max77620_children[0].resume')
> > drivers/mfd/max77620.c:64:2: error: initializer element is not constant
> > DEFINE_MFD_CELL_NAME_RESOURCE("max77620-thermal", thermal_resources),
> > ^
> > drivers/mfd/max77620.c:64:2: note: (near initialization for 'max77620_children[0].platform_data')
> > drivers/mfd/max77620.c:68:2: error: initializer element is not constant
> > DEFINE_MFD_CELL_NAME("max20024-pinctrl"),
> > ^
> > drivers/mfd/max77620.c:68:2: note: (near initialization for 'max20024_children[0].name')
> > drivers/mfd/max77620.c:69:2: error: initializer element is not constant
> > DEFINE_MFD_CELL_NAME_RESOURCE("max20024-gpio", gpio_resources),
> > ^
> > drivers/mfd/max77620.c:69:2: note: (near initialization for 'max20024_children[0].id')
> > drivers/mfd/max77620.c:70:2: error: initializer element is not constant
> > DEFINE_MFD_CELL_NAME("max20024-pmic"),
> > ^
> > drivers/mfd/max77620.c:70:2: note: (near initialization for 'max20024_children[0].usage_count')
> > drivers/mfd/max77620.c:71:2: error: initializer element is not constant
> > DEFINE_MFD_CELL_NAME_RESOURCE("max20024-rtc", rtc_resources),
> > ^
> > drivers/mfd/max77620.c:71:2: note: (near initialization for 'max20024_children[0].enable')
> > drivers/mfd/max77620.c:72:2: error: initializer element is not constant
> > DEFINE_MFD_CELL_NAME_RESOURCE("max20024-power", power_resources),
> > ^
> > drivers/mfd/max77620.c:72:2: note: (near initialization for 'max20024_children[0].disable')
> > drivers/mfd/max77620.c:73:2: error: initializer element is not constant
> > DEFINE_MFD_CELL_NAME("max20024-watchdog"),
> > ^
> > drivers/mfd/max77620.c:73:2: note: (near initialization for 'max20024_children[0].suspend')
> > drivers/mfd/max77620.c:74:2: error: initializer element is not constant
> > DEFINE_MFD_CELL_NAME("max20024-clock"),
> > ^
> > drivers/mfd/max77620.c:74:2: note: (near initialization for 'max20024_children[0].resume')
> > cc1: some warnings being treated as errors
> >
> >vim +/DEFINE_MFD_CELL_NAME +57 drivers/mfd/max77620.c
> >
> > 51 REGMAP_IRQ_REG(MAX77620_IRQ_LBT_MBATLOW, 1, MAX77620_IRQ_LBM_MASK),
> > 52 REGMAP_IRQ_REG(MAX77620_IRQ_LBT_TJALRM1, 1, MAX77620_IRQ_TJALRM1_MASK),
> > 53 REGMAP_IRQ_REG(MAX77620_IRQ_LBT_TJALRM2, 1, MAX77620_IRQ_TJALRM2_MASK),
> > 54 };
> > 55
> > 56 static struct mfd_cell max77620_children[] = {
> > > 57 DEFINE_MFD_CELL_NAME("max77620-pinctrl"),
> > > 58 DEFINE_MFD_CELL_NAME_RESOURCE("max77620-gpio", gpio_resources),
> > 59 DEFINE_MFD_CELL_NAME("max77620-pmic"),
> > 60 DEFINE_MFD_CELL_NAME_RESOURCE("max77620-rtc", rtc_resources),
> > 61 DEFINE_MFD_CELL_NAME_RESOURCE("max77620-power", power_resources),
> >
> >---
> >0-DAY kernel test infrastructure Open Source Technology Center
> >https://lists.01.org/pipermail/kbuild-all Intel Corporation
>
--
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
next prev parent reply other threads:[~2016-02-01 8:26 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-30 16:38 [PATCH V7 0/8] Add support for MAXIM MAX77620/MAX20024 PMIC Laxman Dewangan
2016-01-30 16:38 ` [PATCH V7 1/8] mfd: add device-tree binding doc for PMIC max77620/max20024 Laxman Dewangan
2016-02-09 15:42 ` Lee Jones
2016-02-09 17:56 ` Laxman Dewangan
2016-02-10 13:23 ` Lee Jones
2016-02-10 13:48 ` Laxman Dewangan
2016-02-11 9:26 ` Lee Jones
2016-02-11 10:19 ` Laxman Dewangan
2016-01-30 16:38 ` [PATCH V7 2/8] mfd: max77620: add core driver for MAX77620/MAX20024 Laxman Dewangan
2016-01-30 17:16 ` kbuild test robot
2016-01-30 17:12 ` Laxman Dewangan
2016-02-01 8:25 ` Lee Jones [this message]
2016-02-01 8:31 ` Laxman Dewangan
2016-02-01 9:02 ` Lee Jones
2016-02-01 9:15 ` Laxman Dewangan
2016-01-30 17:52 ` kbuild test robot
2016-01-30 16:38 ` [PATCH V7 3/8] pinctrl: add DT binding doc for pincontrol of PMIC max77620/max20024 Laxman Dewangan
2016-02-05 14:48 ` Linus Walleij
2016-01-30 16:38 ` [PATCH V7 4/8] pinctrl: max77620: add pincontrol driver for MAX77620/MAX20024 Laxman Dewangan
2016-01-30 16:38 ` [PATCH V7 5/8] gpio: add DT binding doc for gpio of PMIC max77620/max20024 Laxman Dewangan
2016-02-05 14:48 ` [rtc-linux] " Linus Walleij
2016-02-09 14:29 ` Lee Jones
2016-01-30 16:38 ` [PATCH V7 6/8] gpio: max77620: add gpio driver for MAX77620/MAX20024 Laxman Dewangan
2016-01-30 16:38 ` [PATCH V7 7/8] regulator: add DT binding doc for regulator of PMIC max77620/max20024 Laxman Dewangan
2016-01-30 16:38 ` [PATCH V7 8/8] regulator: max77620: add regulator driver for max77620/max20024 Laxman Dewangan
2016-02-09 15:02 ` Laxman Dewangan
2016-02-09 15:36 ` Mark Brown
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=20160201082553.GW3368@x1 \
--to=lee.jones@linaro.org \
--cc=a.zummo@towertech.it \
--cc=alexandre.belloni@free-electrons.com \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=gnurou@gmail.com \
--cc=ijc+devicetree@hellion.org.uk \
--cc=k.kozlowski@samsung.com \
--cc=kbuild-all@01.org \
--cc=ldewangan@nvidia.com \
--cc=lgirdwood@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=mark.rutland@arm.com \
--cc=mkasoju@nvidia.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--cc=rtc-linux@googlegroups.com \
--cc=swarren@nvidia.com \
--cc=treding@nvidia.com \
--cc=vreddytalla@nvidia.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).