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)
Date: Mon, 19 Jun 2017 18:34:02 +0100 [thread overview]
Message-ID: <20170619173402.GG10672@ZenIV.linux.org.uk> (raw)
In-Reply-To: <CAMuHMdUspjmRhOJwWXw=t458RnBcG8sPtBe2onUh-sDsCrAkjA@mail.gmail.com>
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...
prev parent reply other threads:[~2017-06-19 17:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-19 13:48 [linux-linus bisection] complete build-i386-pvops osstest service owner
2017-06-19 14:36 ` ufs build failure (no __udivdi3) on i386 in linux tip (edf9364d3f92) Ian Jackson
2017-06-19 14:36 ` Ian Jackson
2017-06-19 15:08 ` Al Viro
2017-06-19 17:22 ` Geert Uytterhoeven
2017-06-19 17:34 ` Al Viro [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170619173402.GG10672@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=arnd@arndb.de \
--cc=axboe@fb.com \
--cc=dushistov@mail.ru \
--cc=geert@linux-m68k.org \
--cc=ian.jackson@eu.citrix.com \
--cc=jic23@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=sfr@canb.auug.org.au \
--cc=torvalds@linux-foundation.org \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.