linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Anton Vorontsov <avorontsov@ru.mvista.com>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
	Ashish Jangam <ashish.jangam@kpitcummins.com>,
	David Dajun Chen <dchen@diasemi.com>
Subject: linux-next: build failure after merge of the battery tree
Date: Mon, 9 Jan 2012 13:11:00 +1100	[thread overview]
Message-ID: <20120109131100.941810596c078b4b6f5740e8@canb.auug.org.au> (raw)

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

Hi Anton,

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

drivers/power/da9052-battery.c: In function 'da9052_bat_read_volt':
drivers/power/da9052-battery.c:293:2: error: implicit declaration of function 'da9052_adc_manual_read' [-Werror=implicit-function-declaration]
drivers/power/da9052-battery.c: In function 'da9052_bat_check_presence':
drivers/power/da9052-battery.c:306:2: error: implicit declaration of function 'da9052_adc_read_temp' [-Werror=implicit-function-declaration]
drivers/power/da9052-battery.c: In function 'da9052_determine_vc_tbl_index':
drivers/power/da9052-battery.c:348:1: warning: control reaches end of non-void function [-Wreturn-type]
cc1: some warnings being treated as errors

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.

I have used the battery tree from next-20120104 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:[~2012-01-09  2:11 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-09  2:11 Stephen Rothwell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-08-21  2:57 linux-next: build failure after merge of the battery tree 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
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  2:31     ` Arun MURTHY
2012-03-26  6:55       ` Linus Walleij
2012-03-26  8:36         ` Anton Vorontsov
2012-03-26  9:00         ` Samuel Ortiz
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-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=20120109131100.941810596c078b4b6f5740e8@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=ashish.jangam@kpitcummins.com \
    --cc=avorontsov@ru.mvista.com \
    --cc=dchen@diasemi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    /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).