From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Guenter Roeck <linux@roeck-us.net>,
Linux-Next <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Trond Myklebust <trond.myklebust@hammerspace.com>,
Arnd Bergmann <arnd@arndb.de>
Subject: Re: linux-next: Tree for Oct 4
Date: Fri, 5 Oct 2018 09:44:45 +1000 [thread overview]
Message-ID: <20181005094445.4d0b68bc@canb.auug.org.au> (raw)
In-Reply-To: <CAMuHMdXfhbFi8HYtqd6BeACyG64_eQvoiSQ7DMpyOmdXEXPymg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1121 bytes --]
Hi Geert,
On Thu, 4 Oct 2018 16:21:42 +0200 Geert Uytterhoeven <geert@linux-m68k.org> wrote:
>
> On Thu, Oct 4, 2018 at 3:47 PM Guenter Roeck <linux@roeck-us.net> wrote:
> > Time for a status report.
> >
> > Build results:
> > total: 135 pass: 121 fail: 14
> > Failed builds:
> > arm:allmodconfig
> > i386:allyesconfig
> > i386:allmodconfig
> > m68k:defconfig
> > m68k:allmodconfig
> > m68k:sun3_defconfig
> > mips:allmodconfig
> > parisc:allmodconfig
> > powerpc:ppc6xx_defconfig
> > s390:defconfig
> > s390:allmodconfig
> > s390:allnoconfig
> > sparc32:allmodconfig
> > xtensa:allmodconfig
>
> Most (all?) 32-bit builds are broken due to commit 571ed1fd2390f74e
> ("SUNRPC: Replace krb5_seq_lock with a lockless scheme"), presumably fixed
> by Arnd's "SUNRPC: use cmpxchg64() in gss_seq_send64_fetch_and_inc"
> (https://lore.kernel.org/patchwork/patch/994909/).
I have added that patch to the nfs tree merge in linux-next today.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2018-10-04 23:44 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-04 8:34 linux-next: Tree for Oct 4 Stephen Rothwell
2018-10-04 13:46 ` Guenter Roeck
2018-10-04 14:21 ` Geert Uytterhoeven
2018-10-04 23:44 ` Stephen Rothwell [this message]
2018-10-05 1:33 ` Guenter Roeck
[not found] ` <01c4a73c-7901-2fbb-8f87-95ff21dc5126-0h96xk9xTtrk1uMJSBkQmQ@public.gmane.org>
2018-10-05 5:39 ` Stephen Rothwell
[not found] ` <20181005153905.126a005e-3FnU+UHB4dNDw9hX6IcOSA@public.gmane.org>
2018-10-05 14:27 ` Alexander Duyck
-- strict thread matches above, loose matches on Subject: below --
2023-10-04 5:21 Stephen Rothwell
2022-10-04 11:05 Stephen Rothwell
2019-10-04 5:59 Stephen Rothwell
2016-10-04 3:56 Stephen Rothwell
2016-10-04 4:22 ` Stephen Rothwell
2013-10-05 22:44 Mark Brown
2013-10-06 18:13 ` Guenter Roeck
2012-10-04 5:33 Stephen Rothwell
2011-10-04 8:11 Stephen Rothwell
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=20181005094445.4d0b68bc@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=arnd@arndb.de \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=trond.myklebust@hammerspace.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).