All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>,
	Liam Girdwood <lrg@slimlogic.co.uk>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
	"Rajendra Nayak" <rnayak@ti.com>,
	"Heiko Stübner" <heiko@sntech.de>
Subject: linux-next: build failure after merge of the regulator tree
Date: Thu, 24 Nov 2011 14:10:46 +1100	[thread overview]
Message-ID: <20111124141046.fdb4b9b923d850b0686924c3@canb.auug.org.au> (raw)

[-- Attachment #1: Type: text/plain, Size: 802 bytes --]

Hi all,

After merging the regulator tree, today's linux-next build (x86_64
allmodconfig) failed like this:

drivers/regulator/gpio-regulator.c: In function 'gpio_regulator_probe':
drivers/regulator/gpio-regulator.c:287:8: error: too few arguments to function 'regulator_register'
include/linux/regulator/driver.h:215:23: note: declared here


Caused by commit 2c043bcbf287 ("regulator: pass additional of_node to
regulator_register()").

drivers/regulator/gpio-regulator.c was added in commit 3f0292ae8bb1
("regulator: Add driver for gpio-controlled regulators") which was
included in Linus' tree before v3.2-rc1.

I have used the regulator tree from next-20111123 for today.
-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/

[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]

             reply	other threads:[~2011-11-24  3:11 UTC|newest]

Thread overview: 62+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-24  3:10 Stephen Rothwell [this message]
2011-11-24  7:31 ` linux-next: build failure after merge of the regulator tree Rajendra Nayak
2012-04-10  3:01 Stephen Rothwell
2012-06-20  4:50 Stephen Rothwell
2012-06-20  4:55 ` Axel Lin
2012-06-20 15:33   ` Stephen Warren
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-09-10  3:20 Stephen Rothwell
2013-07-01  4:18 Stephen Rothwell
2013-07-01  6:07 ` Kishon Vijay Abraham I
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
2014-01-06  6:37 Stephen Rothwell
2014-05-27  4:41 Stephen Rothwell
2014-07-08  3:10 Stephen Rothwell
2014-08-17 20:41 Stephen Rothwell
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
2015-03-10  2:44 Stephen Rothwell
2015-03-10 10:40 ` 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
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
2018-11-20  0:49 Stephen Rothwell
2018-11-20  0:56 ` Dmitry Osipenko
2019-08-29  3:57 Stephen Rothwell
2019-09-03  4:26 Stephen Rothwell
2019-09-03  6:46 ` Bartosz Golaszewski
2020-02-25 23:39 Stephen Rothwell
2021-10-22  1:53 Stephen Rothwell
2021-10-22 10:31 ` Alistair
2021-10-22 12:40   ` Mark Brown
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
2022-07-07  3:01 Stephen Rothwell

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=20111124141046.fdb4b9b923d850b0686924c3@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=heiko@sntech.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=lrg@slimlogic.co.uk \
    --cc=rnayak@ti.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 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.