linux-kernel - Re: linux-next: build failure after merge of the file-locks 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] [thread-next>] [day] [month] [year] [list]

Message-ID: <20170517223557.3b9f78b5@canb.auug.org.au>
Date:   Wed, 17 May 2017 22:35:57 +1000
From:   Stephen Rothwell <sfr@...b.auug.org.au>
To:     Jeff Layton <jlayton@...chiereds.net>
Cc:     Linux-Next Mailing List <linux-next@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Christoph Hellwig <hch@....de>
Subject: Re: linux-next: build failure after merge of the file-locks tree

Hi Jeff,

On Wed, 17 May 2017 08:32:46 -0400 Jeff Layton <jlayton@...chiereds.net> wrote:
>
> On Wed, 2017-05-17 at 11:48 +1000, Stephen Rothwell wrote:
> > 
> > On Tue, 16 May 2017 21:10:03 -0400 Jeff Layton <jlayton@...chiereds.net> wrote:  
> > > 
> > > I think this patch will probably fix it, but I don't have a 32-bit host
> > > set up to build on just now. I'll go ahead and merge this into the
> > > branch, and will plan to test it tomorrow (hopefully before the next
> > > fetch).  
> > 
> > Thanks.  If you don't get around to testing, I will let you know if it
> > still fails tomorrow :-)
> 
> Yep, that fixes it (at least on i386). I squashed it into patch 1 of
> Christoph's series. Please let me know if you see further problems.

Thanks, will do.

-- 
Cheers,
Stephen Rothwell