linux-kernel - Re: linux-next: build failure after merge of the pm 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]

Date:	Fri, 27 Jan 2012 10:35: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,
	Alex Frid <afrid@...dia.com>,
	Antti Miettinen <amiettinen@...dia.com>,
	Diwakar Tundlam <dtundlam@...dia.com>,
	Scott Williams <scwilliams@...dia.com>,
	"Yu-Huan Hsu" <yhsu@...dia.com>, markgross <markgross@...gnar.org>,
	Linux PM mailing list <linux-pm@...r.kernel.org>
Subject: Re: linux-next: build failure after merge of the pm tree

On Friday, January 27, 2012, Stephen Rothwell wrote:
> Hi Rafael,
> 
> After merging the pm tree, today's linux-next build (powerpc
> ppc64_defconfig) failed like this:
> 
> kernel/power/process.c: In function 'thaw_kernel_threads':
> kernel/power/process.c:199:2: error: 'g' undeclared (first use in this function)
> kernel/power/process.c:199:2: note: each undeclared identifier is reported only once for each function it appears in
> kernel/power/process.c:199:2: error: 'p' undeclared (first use in this function)
> 
> Caused by commit 625278ca8016 ("PM / QoS: Simplify PM QoS expansion/merge").
> 
> Clearly never built :-(  At least, not in this form.
> 
> I have used the pm tree from next-20120125 for today.

Sorry for the breakage.

I took a broken version of that patch from my quilt queue by mistake,
should be fixed 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/