From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Liam Girdwood <lrg@slimlogic.co.uk>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Linus Walleij <linus.walleij@linaro.org>,
Peter Ujfalusi <peter.ujfalusi@ti.com>,
Samuel Ortiz <sameo@linux.intel.com>,
Balaji T K <balajitk@ti.com>
Subject: Re: linux-next: build failure after merge of the final tree (regulator tree related)
Date: Fri, 3 Feb 2012 11:02:35 +0000 [thread overview]
Message-ID: <20120203110234.GC3151@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <20120203161522.c079159878788e9ba7e7b242@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 1119 bytes --]
On Fri, Feb 03, 2012 at 04:15:22PM +1100, Stephen Rothwell wrote:
> drivers/mfd/twl-core.c: In function 'add_children':
> drivers/mfd/twl-core.c:752:10: error: 'struct regulator_consumer_supply' has no member named 'dev'
> drivers/mfd/twl-core.c:753:10: error: 'struct regulator_consumer_supply' has no member named 'dev'
> drivers/mfd/twl-core.c:754:10: error: 'struct regulator_consumer_supply' has no member named 'dev'
> drivers/mfd/twl-core.c:800:10: error: 'struct regulator_consumer_supply' has no member named 'dev'
> Caused by commit 737f360d5bef ("regulator: Remove support for supplies
> specified by struct device").
For stuff like this where it's clear that there's an issue with the
side where the failure is noticed it's helpful to also let the people
working on the driver side know - it can make things work better with
timezones. Unfortunately the TWL driver is both very interesting and
not really getting TLC so it's not a great example here but still. I've
CCed a bunch of random people who show up in the commit log plus Samuel.
I'll fix up this up and carry a patch via the regulator tree.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-02-03 11:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-03 5:15 linux-next: build failure after merge of the final tree (regulator tree related) Stephen Rothwell
2012-02-03 11:02 ` Mark Brown [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-04-16 5:52 Stephen Rothwell
2012-04-17 4:27 Stephen Rothwell
2012-04-17 13:55 ` Mark Brown
2012-08-16 5:16 Stephen Rothwell
2012-08-16 6:39 ` Arnd Bergmann
2012-08-16 10:58 ` 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=20120203110234.GC3151@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=balajitk@ti.com \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=lrg@slimlogic.co.uk \
--cc=peter.ujfalusi@ti.com \
--cc=sameo@linux.intel.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).