From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Anton Vorontsov <cbouatmailru@gmail.com>
Cc: Ashish Jangam <ashish.jangam@kpitcummins.com>,
Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org
Subject: Re: linux-next: build failure after merge of the battery tree
Date: Mon, 9 Jan 2012 23:53:18 +0000 [thread overview]
Message-ID: <20120109235318.GJ30766@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <20120109131037.GA26091@oksana.dev.rtsoft.ru>
On Mon, Jan 09, 2012 at 05:10:37PM +0400, Anton Vorontsov wrote:
> On Mon, Jan 09, 2012 at 01:59:29PM +0530, Ashish Jangam wrote:
> > > Caused by commit ded7fc7b0550 ("power_supply: Add DA9052 battery driver").
> > > The commit message says "This driver depends on DA9052 MFD core dirver for definitions and methods". That core is presumably still pending inclusion.
> Well, it is in the MFD tree already, otherwise allmodconfig would not
> be able to select this driver.
It didn't actually go in via the MFD tree, it went in via regmap, but
same difference.
> > > I have used the battery tree from next-20120104 for today.
> > This patch depends upon Da9052/53 MFD core and also on one of its incremental patch for ADC that got these functions definitions. Below is that patch.
> > We had already posted this patch.
> So, this patch should go via MFD tree asap. Otherwise, I'll have to
> disable this driver by making it depend on 'broken' in Kconfig.
The regmap tree has already been merged by Linus which makes things a
bit tricky, it'd probably need to wait for -rc1 for Samuel to send it
givne that Linus was saying he really wanted everything to have been in
-next before the merge window.
next prev parent reply other threads:[~2012-01-09 23:53 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <C3AE124F08223B42BC95AEB82F0F6CED1FDB2C78@KCHJEXMB02.kpit.com>
2012-01-09 8:29 ` Re:linux-next: build failure after merge of the battery tree Ashish Jangam
2012-01-09 13:10 ` linux-next: " Anton Vorontsov
2012-01-09 23:53 ` Mark Brown [this message]
2012-01-10 0:51 ` Anton Vorontsov
2023-08-21 2:57 Stephen Rothwell
2023-08-21 7:07 ` Lee Jones
2023-08-21 7:13 ` Lee Jones
2023-08-21 12:41 ` Rob Herring
2023-08-21 12:46 ` Lee Jones
-- strict thread matches above, loose matches on Subject: below --
2022-06-20 0:45 Stephen Rothwell
2022-06-21 12:30 ` Asmaa Mnebhi
2022-06-24 2:47 ` Stephen Rothwell
2022-06-24 12:44 ` Asmaa Mnebhi
2022-06-28 2:30 ` Stephen Rothwell
2022-05-04 2:35 Stephen Rothwell
2019-12-19 0:01 Stephen Rothwell
2019-12-19 1:35 ` Sebastian Reichel
2019-06-28 4:03 Stephen Rothwell
2019-06-28 15:31 ` Sebastian Reichel
2019-06-28 16:56 ` Enric Balletbo i Serra
2019-06-29 0:33 ` Stephen Rothwell
2019-07-01 13:22 ` Enric Balletbo i Serra
2015-09-29 1:45 Stephen Rothwell
2015-10-02 1:49 ` Stephen Rothwell
2015-10-08 1:04 ` Stephen Rothwell
2015-10-08 6:12 ` Belisko Marek
2015-10-08 10:21 ` Stephen Rothwell
2015-10-15 14:26 ` Stephen Rothwell
2015-10-20 22:32 ` Stephen Rothwell
2015-10-21 6:12 ` Belisko Marek
2015-07-27 1:40 Stephen Rothwell
2012-07-16 4:09 Stephen Rothwell
2012-07-16 4:57 ` Chanwoo Choi
2012-03-15 2:56 Stephen Rothwell
2012-03-20 4:39 ` Stephen Rothwell
2012-03-26 2:13 ` Stephen Rothwell
2012-03-26 16:11 ` Anton Vorontsov
2012-03-26 21:44 ` Stephen Rothwell
2012-03-26 21:47 ` Stephen Rothwell
2012-03-27 13:03 ` Anton Vorontsov
2012-03-28 11:38 ` Mark Brown
2012-01-09 2:11 Stephen Rothwell
2012-01-05 3:40 Stephen Rothwell
2012-01-05 15:25 ` Anton Vorontsov
2012-01-05 15:53 ` Greg KH
2012-01-07 9:00 ` Jeremy Fitzhardinge
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=20120109235318.GJ30766@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=ashish.jangam@kpitcummins.com \
--cc=cbouatmailru@gmail.com \
--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).