linux-kernel - Re: linux-next: build failure in Linus' 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: <CA+55aFxJjt_vTe4UXhfq7O4r0gCWbAj7FAFrNjpk9Tf0RD86rA@mail.gmail.com>
Date:	Thu, 26 Jul 2012 18:04:30 -0700
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
Cc:	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
	Alexander Block <ablock84@...glemail.com>,
	David Sterba <dave@...os.cz>, Arne Jansen <sensille@....net>,
	Jan Schmidt <list.btrfs@...-o-sch.net>,
	Alex Lyakas <alex.bolshoy.btrfs@...il.com>,
	Chris Mason <chris.mason@...ionio.com>
Subject: Re: linux-next: build failure in Linus' tree

On Thu, Jul 26, 2012 at 5:15 PM, Stephen Rothwell <sfr@...b.auug.org.au> wrote:
>
> After merging the origin tree, today's linux-next build (powerpc
> ppc64_defconfig) failed like this:

Oh well. I did an x86-64 build after that pull (because of the need
for that semantic merge thing), but apparently x86-64 gets the
vmalloc.h indirectly through some other header.

          Linus
--
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/