From: Kishon Vijay Abraham I <kishon@ti.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>, Keerthy <a0393675@ti.com>
Cc: Mark Brown <broonie@kernel.org>,
Liam Girdwood <lgirdwood@gmail.com>, <linux-next@vger.kernel.org>,
<linux-kernel@vger.kernel.org>,
Laxman Dewangan <ldewangan@nvidia.com>
Subject: Re: linux-next: build failure after merge of the regulator tree
Date: Mon, 1 Jul 2013 11:37:09 +0530 [thread overview]
Message-ID: <51D11C8D.2010400@ti.com> (raw)
In-Reply-To: <20130701141827.8f9122f0b6ca860fa5fd11a5@canb.auug.org.au>
+Keerthy
On Monday 01 July 2013 09:48 AM, Stephen Rothwell wrote:
> Hi all,
>
> After merging the regulator tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> drivers/regulator/palmas-regulator.c: In function 'palmas_regulators_probe':
> drivers/regulator/palmas-regulator.c:850:8: error: 'PALMAS_REG_SMPS10' undeclared (first use in this function)
> case PALMAS_REG_SMPS10:
> ^
>
> Caused by commit 07a02e0b1a4f ("regulator: palmas: model SMPS10 as two
> regulators"). Clearly not build tested at all :-( Grep is your
> friend ...
commit 1ffb0b (mfd: palmas: Add SMPS10_BOOST feature) had used PALMAS_REG_SMPS10
and I dint have that patch in my tree. Sorry, my bad.
Keerthy will send a fix for it.
Thanks
Kishon
WARNING: multiple messages have this Message-ID (diff)
From: Kishon Vijay Abraham I <kishon@ti.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>, Keerthy <a0393675@ti.com>
Cc: Mark Brown <broonie@kernel.org>,
Liam Girdwood <lgirdwood@gmail.com>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Laxman Dewangan <ldewangan@nvidia.com>
Subject: Re: linux-next: build failure after merge of the regulator tree
Date: Mon, 1 Jul 2013 11:37:09 +0530 [thread overview]
Message-ID: <51D11C8D.2010400@ti.com> (raw)
In-Reply-To: <20130701141827.8f9122f0b6ca860fa5fd11a5@canb.auug.org.au>
+Keerthy
On Monday 01 July 2013 09:48 AM, Stephen Rothwell wrote:
> Hi all,
>
> After merging the regulator tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> drivers/regulator/palmas-regulator.c: In function 'palmas_regulators_probe':
> drivers/regulator/palmas-regulator.c:850:8: error: 'PALMAS_REG_SMPS10' undeclared (first use in this function)
> case PALMAS_REG_SMPS10:
> ^
>
> Caused by commit 07a02e0b1a4f ("regulator: palmas: model SMPS10 as two
> regulators"). Clearly not build tested at all :-( Grep is your
> friend ...
commit 1ffb0b (mfd: palmas: Add SMPS10_BOOST feature) had used PALMAS_REG_SMPS10
and I dint have that patch in my tree. Sorry, my bad.
Keerthy will send a fix for it.
Thanks
Kishon
next prev parent reply other threads:[~2013-07-01 6:07 UTC|newest]
Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-01 4:18 linux-next: build failure after merge of the regulator tree Stephen Rothwell
2013-07-01 6:07 ` Kishon Vijay Abraham I [this message]
2013-07-01 6:07 ` Kishon Vijay Abraham I
2013-07-01 8:43 ` Mark Brown
2013-07-01 8:47 ` Kishon Vijay Abraham I
2013-07-01 8:47 ` Kishon Vijay Abraham I
2013-07-01 8:42 ` Mark Brown
-- strict thread matches above, loose matches on Subject: below --
2022-07-07 3:01 Stephen Rothwell
2021-11-23 7:41 Stephen Rothwell
2021-11-23 8:33 ` Vaittinen, Matti
2021-11-23 9:26 ` Vaittinen, Matti
2021-11-23 14:17 ` Mark Brown
2021-10-22 1:53 Stephen Rothwell
2021-10-22 10:31 ` Alistair
2021-10-22 12:40 ` Mark Brown
2020-02-25 23:39 Stephen Rothwell
2019-09-03 4:26 Stephen Rothwell
2019-09-03 6:46 ` Bartosz Golaszewski
2019-08-29 3:57 Stephen Rothwell
2018-11-20 0:49 Stephen Rothwell
2018-11-20 0:56 ` Dmitry Osipenko
2017-02-01 2:42 Stephen Rothwell
2017-02-01 10:03 ` Mark Brown
2017-02-02 22:30 ` Stephen Rothwell
2017-02-03 11:31 ` Mark Brown
2015-04-09 4:33 Stephen Rothwell
2015-04-09 9:35 ` Mark Brown
2015-04-13 23:44 ` Stephen Rothwell
2015-04-14 1:07 ` Bjorn Andersson
2015-04-14 1:22 ` Stephen Rothwell
2015-04-14 9:40 ` Mark Brown
2015-04-15 3:03 ` Dave Airlie
2015-04-09 15:00 ` Rob Clark
2015-03-10 2:44 Stephen Rothwell
2015-03-10 10:40 ` Mark Brown
2014-09-08 8:33 Stephen Rothwell
2014-09-09 22:39 ` Mark Brown
2014-09-10 2:33 ` Chris Zhong
2014-09-10 10:54 ` Mark Brown
2014-09-10 2:50 ` Doug Anderson
2014-08-17 20:41 Stephen Rothwell
2014-07-08 3:10 Stephen Rothwell
2014-05-27 4:41 Stephen Rothwell
2014-01-06 6:37 Stephen Rothwell
2012-09-10 3:20 Stephen Rothwell
2012-06-21 3:27 Stephen Rothwell
2012-06-21 8:13 ` Kim, Milo
2012-06-21 8:20 ` Axel Lin
2012-06-21 8:42 ` Kim, Milo
2012-06-21 9:14 ` Mark Brown
2012-06-21 11:04 ` Stephen Rothwell
2012-06-21 11:04 ` Stephen Rothwell
2012-06-21 11:30 ` Mark Brown
2012-06-21 17:35 ` Andrew Morton
2012-06-21 17:35 ` Andrew Morton
2012-06-21 9:46 ` Mark Brown
2012-06-20 4:50 Stephen Rothwell
2012-06-20 4:55 ` Axel Lin
2012-06-20 15:33 ` Stephen Warren
2012-04-10 3:01 Stephen Rothwell
2011-11-24 3:10 Stephen Rothwell
2011-11-24 7:31 ` Rajendra Nayak
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=51D11C8D.2010400@ti.com \
--to=kishon@ti.com \
--cc=a0393675@ti.com \
--cc=broonie@kernel.org \
--cc=ldewangan@nvidia.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.