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:	Mon, 14 Jan 2013 19:54:53 +0100
From:	"Rafael J. Wysocki" <rjw@...k.pl>
To:	sedat.dilek@...il.com
Cc:	Stephen Rothwell <sfr@...b.auug.org.au>,
	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: linux-next: build failure after merge of the pm tree

On Monday, January 14, 2013 02:22:20 PM Sedat Dilek wrote:
> On Mon, Jan 14, 2013 at 1:03 AM, Stephen Rothwell <sfr@...b.auug.org.au> wrote:
> > Hi Rafael,
> >
> > After merging the pm tree, today's linux-next build (powerpc
> > ppc64_defconfig) failed like this:
> >
> > In file included from init/main.c:25:0:
> > include/linux/acpi.h:549:46: error: unknown type name 'acpi_handle'
> > include/linux/acpi.h:551:49: error: unknown type name 'acpi_handle'
> >
> > and many more.
> >
> > Caused by commit c9b147cd9648 ("ACPI / PM: Rework the handling of devices
> > depending on power resources").  Please check with and without CONFIG
> > options that affect patches ...
> >
> > I have used the pm tree from next-20130111 for today.
> 
> [ Please also CC linux-next ML ! ]
> 
> [ QUOTE ]
> Thanks for the report and sorry for the breakage.  Should be fixed now.
> 
> Rafael
> [ /QUOTE ]
> 
> What was the cause for this?
> 
> Did you refresh "ACPI / PM: Rework the handling of devices depending
> on power resources" [1]?

I did.

Thanks,
Rafael


-- 
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
--
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/