linux-kernel - Re: linux-next: build failure after merge of the final tree (pm tree related)

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: <201112230132.58765.rjw@sisk.pl>
Date:	Fri, 23 Dec 2011 01:32:58 +0100
From:	"Rafael J. Wysocki" <rjw@...k.pl>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
Cc:	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: linux-next: build failure after merge of the final tree (pm tree related)

On Thursday, December 22, 2011, Stephen Rothwell wrote:
> Hi ,
> 
> After merging the final tree, today's linux-next build (powerpc
> allnoconfig) failed like this:
> 
> drivers/base/bus.o: In function `dev_pm_qos_add_ancestor_request':
> bus.c:(.text+0x4c0): multiple definition of `dev_pm_qos_add_ancestor_request'
> drivers/base/core.o:core.c:(.text+0x8ec): first defined here
> drivers/base/dd.o: In function `dev_pm_qos_add_ancestor_request':
> dd.c:(.text+0x418): multiple definition of `dev_pm_qos_add_ancestor_request'
> drivers/base/core.o:core.c:(.text+0x8ec): first defined here
> kernel/sysctl_binary.o: In function `dev_pm_qos_add_ancestor_request':
> sysctl_binary.c:(.text+0x124): multiple definition of `dev_pm_qos_add_ancestor_request'
> 
> Caused by commit 513dcbda6199 ("PM / QoS: Introduce
> dev_pm_qos_add_ancestor_request()") from the pm tree.
> 
> Please build with and without config options that protect new code ... :-(

My bad, sorry.

This issue should be fixed in my linux-next branch now.

Thanks,
Rafael
--
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/