From mboxrd@z Thu Jan 1 00:00:00 1970 From: Geert Uytterhoeven Subject: Re: ufs build failure (no __udivdi3) on i386 in linux tip (edf9364d3f92) Date: Mon, 19 Jun 2017 19:22:39 +0200 Message-ID: References: <22855.57727.390987.969954@mariner.uk.xensource.com> <20170619150818.GC10672@ZenIV.linux.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Return-path: In-Reply-To: <20170619150818.GC10672@ZenIV.linux.org.uk> Sender: linux-kernel-owner@vger.kernel.org To: Al Viro Cc: Ian Jackson , Evgeniy Dushistov , xen-devel@lists.xensource.com, Linus Torvalds , Jonathan Cameron , Jens Axboe , Linux FS Devel , "linux-kernel@vger.kernel.org" , Stephen Rothwell , Arnd Bergmann , Guenter Roeck List-Id: xen-devel@lists.xenproject.org Hi Al, On Mon, Jun 19, 2017 at 5:08 PM, Al Viro wrote: > Fixed in vfs.git#ufs-fixes; see commit 77e9ce327d9b607cd6e57c0f4524a654dc59c4b1 > there. Not sure if it's worth splitting... I can confirm that commit fixes the build for m68k. Let's hope it fixes the build for all other 32-bit platforms, too ;-) If I'm not mistaken, the commit that caused the breakage was never part of linux-next before it entered mainline? Can you please make sure all commits cook a few days in linux-next before they are sent upstream? Thanks! Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds