From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeff Layton Subject: Re: linux-next: build failure after merge of the file-locks tree Date: Wed, 17 May 2017 08:32:46 -0400 Message-ID: <1495024366.2930.2.camel@poochiereds.net> References: <20170517102752.3bd4da91@canb.auug.org.au> <1494983403.21644.8.camel@poochiereds.net> <20170517114805.57714a7a@canb.auug.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20170517114805.57714a7a@canb.auug.org.au> Sender: linux-kernel-owner@vger.kernel.org To: Stephen Rothwell Cc: Linux-Next Mailing List , Linux Kernel Mailing List , Christoph Hellwig List-Id: linux-next.vger.kernel.org On Wed, 2017-05-17 at 11:48 +1000, Stephen Rothwell wrote: > Hi Jeff, > > On Tue, 16 May 2017 21:10:03 -0400 Jeff Layton 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! -- Jeff Layton