From: Stephen Warren <swarren@wwwdotorg.org>
To: axel.lin@gmail.com, Grant Likely <grant.likely@secretlab.ca>,
Linus Walleij <linus.walleij@linaro.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Mark Brown <broonie@opensource.wolfsonmicro.com>,
Liam Girdwood <lrg@ti.com>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org, "Kim,
Milo" <Milo.Kim@ti.com>
Subject: Re: linux-next: build failure after merge of the regulator tree
Date: Wed, 20 Jun 2012 09:33:23 -0600 [thread overview]
Message-ID: <4FE1ED43.3000509@wwwdotorg.org> (raw)
In-Reply-To: <CAF+7xWkMSuS3hcWMjKX8OdaLW038eQ-Es+WZeVja3iUiTXMWeQ@mail.gmail.com>
On 06/19/2012 10:55 PM, Axel Lin wrote:
> 2012/6/20 Stephen Rothwell <sfr@canb.auug.org.au>:
>> Hi all,
>>
>> After merging the regulator tree, today's linux-next build (x86_64
>> allmodconfig) failed like this:
>>
>> ERROR: "devm_gpio_request_one" [drivers/regulator/lp872x.ko] undefined!
>>
>> Caused by commit af8b5fc31099 ("regulator: add new regulator driver for
>> lp872x").
>
> Milo already sent a patch for this:
>
> [PATCH] gpio: add EXPORT_SYMBOL() for devm_gpio_request_one
> https://lkml.org/lkml/2012/6/19/58
As did I earlier:
https://lkml.org/lkml/2012/6/7/601
I hope that can go into 3.5, since the issue shows up there when
building Tegra audio as modules.
next prev parent reply other threads:[~2012-06-20 15:33 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-20 4:50 linux-next: build failure after merge of the regulator tree Stephen Rothwell
2012-06-20 4:55 ` Axel Lin
2012-06-20 15:33 ` Stephen Warren [this message]
-- 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
2013-07-01 4:18 Stephen Rothwell
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:42 ` Mark Brown
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:30 ` Mark Brown
2012-06-21 17:35 ` Andrew Morton
2012-06-21 9:46 ` Mark Brown
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=4FE1ED43.3000509@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=Milo.Kim@ti.com \
--cc=axel.lin@gmail.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=grant.likely@secretlab.ca \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=lrg@ti.com \
--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 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).