From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1751119AbdFSReO (ORCPT <rfc822;w@1wt.eu>);
        Mon, 19 Jun 2017 13:34:14 -0400
Received: from zeniv.linux.org.uk ([195.92.253.2]:42264 "EHLO
        ZenIV.linux.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S1751017AbdFSReN (ORCPT
        <rfc822;linux-kernel@vger.kernel.org>);
        Mon, 19 Jun 2017 13:34:13 -0400
Date: Mon, 19 Jun 2017 18:34:02 +0100
From: Al Viro <viro@ZenIV.linux.org.uk>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Ian Jackson <ian.jackson@eu.citrix.com>,
        Evgeniy Dushistov <dushistov@mail.ru>, xen-devel@lists.xensource.com,
        Linus Torvalds <torvalds@linux-foundation.org>,
        Jonathan Cameron <jic23@kernel.org>, Jens Axboe <axboe@fb.com>,
        Linux FS Devel <linux-fsdevel@vger.kernel.org>,
        "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
        Stephen Rothwell <sfr@canb.auug.org.au>, Arnd Bergmann <arnd@arndb.de>,
        Guenter Roeck <linux@roeck-us.net>
Subject: Re: ufs build failure (no __udivdi3) on i386 in linux tip
 (edf9364d3f92)
Message-ID: <20170619173402.GG10672@ZenIV.linux.org.uk>
References: <E1dMx2x-0007xW-D8@osstest.test-lab.xenproject.org>
 <22855.57727.390987.969954@mariner.uk.xensource.com>
 <20170619150818.GC10672@ZenIV.linux.org.uk>
 <CAMuHMdUspjmRhOJwWXw=t458RnBcG8sPtBe2onUh-sDsCrAkjA@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAMuHMdUspjmRhOJwWXw=t458RnBcG8sPtBe2onUh-sDsCrAkjA@mail.gmail.com>
User-Agent: Mutt/1.8.0 (2017-02-23)
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

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...