Re: ufs build failure (no __udivdi3) on i386 in linux tip (edf9364d3f92)

From	Al Viro <viro@ZenIV.linux.org.uk>
Newsgroups	linux.kernel
Subject	Re: ufs build failure (no __udivdi3) on i386 in linux tip (edf9364d3f92)
Date	2017-06-19 19:40 +0200
Message-ID	<tU8OC-5H3-13@gated-at.bofh.it> (permalink)
References	<tU60q-3Pk-19@gated-at.bofh.it> <tU60q-3Pk-17@gated-at.bofh.it> <tU6ts-4hT-33@gated-at.bofh.it> <tU8EW-5CR-31@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Show all headers | View raw

On Mon, Jun 19, 2017 at 07:22:39PM +0200, Geert Uytterhoeven wrote:
> Hi Al,
> 
> On Mon, Jun 19, 2017 at 5:08 PM, Al Viro <viro@zeniv.linux.org.uk> 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?

It's not an excuse, but I got too used to 0-day buildbot catching that kind
of stuff within a day or so ;-/  Should've done cross-builds myself, of course -
my fault...

Back to linux.kernel | Previous | Next — Previous in thread | Find similar | Unroll thread

Thread

ufs build failure (no __udivdi3) on i386 in linux tip (edf9364d3f92) Ian Jackson <ian.jackson@eu.citrix.com> - 2017-06-19 16:40 +0200
  Re: ufs build failure (no __udivdi3) on i386 in linux tip  (edf9364d3f92) Al Viro <viro@ZenIV.linux.org.uk> - 2017-06-19 17:10 +0200
    Re: ufs build failure (no __udivdi3) on i386 in linux tip (edf9364d3f92) Geert Uytterhoeven <geert@linux-m68k.org> - 2017-06-19 19:30 +0200
      Re: ufs build failure (no __udivdi3) on i386 in linux tip  (edf9364d3f92) Al Viro <viro@ZenIV.linux.org.uk> - 2017-06-19 19:40 +0200

csiph-web