[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20170619173402.GG10672@ZenIV.linux.org.uk>
Date: Mon, 19 Jun 2017 18:34:02 +0100
From: Al Viro <viro@...IV.linux.org.uk>
To: Geert Uytterhoeven <geert@...ux-m68k.org>
Cc: Ian Jackson <ian.jackson@...citrix.com>,
Evgeniy Dushistov <dushistov@...l.ru>,
xen-devel@...ts.xensource.com,
Linus Torvalds <torvalds@...ux-foundation.org>,
Jonathan Cameron <jic23@...nel.org>, Jens Axboe <axboe@...com>,
Linux FS Devel <linux-fsdevel@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Stephen Rothwell <sfr@...b.auug.org.au>,
Arnd Bergmann <arnd@...db.de>,
Guenter Roeck <linux@...ck-us.net>
Subject: Re: ufs build failure (no __udivdi3) on i386 in linux tip
(edf9364d3f92)
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@...iv.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...
Powered by blists - more mailing lists