From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
ashishj3 <ashish.jangam@kpitcummins.com>,
Grant Likely <grant.likely@secretlab.ca>,
David Dajun Chen <dchen@diasemi.com>
Subject: Re: linux-next: build failure after merge of the regmap tree
Date: Thu, 15 Dec 2011 06:17:57 +0000 [thread overview]
Message-ID: <20111215061757.GC24287@sirena.org.uk> (raw)
In-Reply-To: <20111215170517.0b7fc08487881743ca76c192@canb.auug.org.au>
On Thu, Dec 15, 2011 at 05:05:17PM +1100, Stephen Rothwell wrote:
> drivers/gpio/gpio-da9052.c:25:35: fatal error: linux/mfd/da9052/gpio.h: No such file or directory
> So, it looks like this would never have built
> (include/linux/mfd/da9052/gpio.h never existed) but noone ever enabled
> CONFIG_PMIC_DA9052 before (which CONFIG_GPIO_DA9052 depends on).
> drivers/gpio/gpio-da9052.c was added with commit 07bfc9152365 ("GPIO:
> DA9052 GPIO module v3") in v3.1-rc1.
The issue here is that the GPIO driver was merged prior to review being
completed for the MFD and then problems with the MFD caused lots of
changes in the rest of the series. The MFD review is now fine so it's
been merged (via regmap due to use of new regmap features) but the GPIO
driver needs updating.
Ashish or Daneil, could you please send a patch fixing this? Possibly
just a case of adding the new header.
next prev parent reply other threads:[~2011-12-15 6:17 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-15 6:05 linux-next: build failure after merge of the regmap tree Stephen Rothwell
2011-12-15 6:17 ` Mark Brown [this message]
2011-12-15 6:24 ` Ashish Jangam
-- strict thread matches above, loose matches on Subject: below --
2020-11-27 7:24 Stephen Rothwell
2020-11-30 17:59 ` Mark Brown
2020-11-30 18:07 ` Pierre-Louis Bossart
2020-11-30 18:11 ` Mark Brown
2020-11-30 18:21 ` Pierre-Louis Bossart
2017-11-02 0:57 Stephen Rothwell
2012-04-11 4:13 Stephen Rothwell
2012-04-11 8:17 ` Mark Brown
2012-02-27 4:05 Stephen Rothwell
[not found] <C3AE124F08223B42BC95AEB82F0F6CED1F9D0895@KCHJEXMB01.kpit.com>
2011-12-15 9:25 ` Ashish Jangam
2011-12-15 18:25 ` Grant Likely
2011-12-16 7:19 ` Ashish Jangam
2011-12-16 8:11 ` Grant Likely
2011-12-16 8:15 ` Ashish Jangam
2011-12-16 8:25 ` Grant Likely
2011-12-15 6:17 Stephen Rothwell
2011-09-29 5:18 Stephen Rothwell
2011-09-29 9:43 ` 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=20111215061757.GC24287@sirena.org.uk \
--to=broonie@opensource.wolfsonmicro.com \
--cc=ashish.jangam@kpitcummins.com \
--cc=dchen@diasemi.com \
--cc=grant.likely@secretlab.ca \
--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 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).