linux-kernel - Re: linux-next: build failure after merge of the battery tree

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-id: <50039F24.60102@samsung.com>
Date:	Mon, 16 Jul 2012 13:57:08 +0900
From:	Chanwoo Choi <cw00.choi@...sung.com>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
Cc:	Anton Vorontsov <avorontsov@...mvista.com>,
	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
	Myungjoo Ham <myungjoo.ham@...sung.com>,
	Kyungmin Park <kyungmin.park@...sung.com>
Subject: Re: linux-next: build failure after merge of the battery tree

Hi Stephen,

On 07/16/2012 01:09 PM, Stephen Rothwell wrote:

> Hi Anton,
> 
> After merging the battery tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
> 
> drivers/built-in.o: In function `charger_manager_probe':
> charger-manager.c:(.text+0x11d61a): undefined reference to `extcon_register_interest'
> charger-manager.c:(.text+0x11d7b6): undefined reference to `extcon_unregister_interest'
> drivers/built-in.o: In function `charger_manager_remove':
> charger-manager.c:(.devexit.text+0x8f3): undefined reference to `extcon_unregister_interest'
> 
> Caused by commit bee737bccb03 ("charger-manager: Use EXTCON Subsystem to
> detect charger cables for charging").
> 
> I have used the battery tree from next-20120713 for today.


I'm so sorry, It is my mistake.
So, I resend below patch to fix build break of charger-manager.
- http://lkml.org/lkml/2012/7/16/5

Best Regards,
Chanwoo Choi
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/