linux-kernel - Re: linux-next: build failure after merge of the slave-dma 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 for Android: free password hash cracker in your pocket

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

Message-ID: <20130402013826.GK10326@intel.com>
Date:	Tue, 2 Apr 2013 07:08:26 +0530
From:	Vinod Koul <vinod.koul@...el.com>
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 slave-dma tree

On Tue, Apr 02, 2013 at 12:57:11PM +1100, Stephen Rothwell wrote:
> Hi Vinod,
> 
> After merging the slave-dma tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
> 
> In file included from include/linux/netdevice.h:38:0,
>                  from arch/x86/net/bpf_jit_comp.c:12:
> include/linux/dmaengine.h:973:1: error: expected identifier or '(' before '>>' token
> 
> And many, many more :-(
> 
> Caused by commit 896b29f155cf ("Merge branch 'for-linus' into next").
> 
> Please at least build test your tree *before* publishing it :-(
Sorry, I had fixed it up early today but looks like have push didnt happen.
Its pushed now

> 
> I have used the slave-dma tree from next-20130328 for today.
> -- 
> Cheers,
> Stephen Rothwell                    sfr@...b.auug.org.au



Download attachment "signature.asc" of type "application/pgp-signature" (837 bytes)