linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linux-Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Tree for Oct 5
Date: Fri, 5 Oct 2018 06:48:54 -0700	[thread overview]
Message-ID: <20181005134854.GA17709@roeck-us.net> (raw)
In-Reply-To: <20181005163943.3f8d4f32@canb.auug.org.au>

On Fri, Oct 05, 2018 at 04:39:43PM +1000, Stephen Rothwell wrote:
> Hi all,
> 
> Changes since 20181004:
> 
> I added a supplied patch to the dma-mapping tree to fix overnight boot
> problems.
> 
> I added a supplied patch to the nfs tree to fix an overnight build
> problem.
> 
> The nfsd tree gained a build failure due to an interaction with the nfs
> tree for which I applied a merge fix patch. And another build failure
> so I used the version from next-20181004.
> 
> The bpf-next tree lost its build failure.
> 
> The drm-msm tree gained a build failure, so I used the version from
> next-20181004.
> 
> The tty tree lost its build failure.
> 
> The slave-dma tree lost its build failure.
> 
> The akpm-current tree gained a conflict against the btrfs-kdave tree.
> 
> The akpm tree gained a build failure due to an interaction with the
> powerpc tree for which I added a merge fix patch.
> 
> Non-merge commits (relative to Linus' tree): 8415
>  8136 files changed, 377585 insertions(+), 173429 deletions(-)
> 

Build results:
	total: 135 pass: 129 fail: 6
Failed builds: 
	mips:allmodconfig 
	powerpc:ppc6xx_defconfig
	s390:defconfig 
	s390:allmodconfig 
	s390:allnoconfig 
	sparc32:allmodconfig 
Qemu test results:
	total: 318 pass: 315 fail: 3
Failed tests: 
	s390:defconfig:initrd 
	s390:defconfig:virtio-blk-ccw:rootfs 
	s390:defconfig:scsi[virtio-ccw]:rootfs

---
mips:allmodconfig, powerpc:ppc6xx_defconfig;

net/sunrpc/auth_gss/gss_krb5_seal.c: In function 'gss_seq_send64_fetch_and_inc':
net/sunrpc/auth_gss/gss_krb5_seal.c:144:3: error:
	implicit declaration of function 'cmpxchg64'

---
s390:

s390-linux-ld:./arch/s390/kernel/vmlinux.lds:41: syntax error

qemu tests also affected. Fixed with:

https://lore.kernel.org/patchwork/patch/993576/

---
sparc32:allmodconfig:

Various "relocation truncated to fit" errors. Also seen in mainline.
It is probably time to drop the build.

---

Guenter

  reply	other threads:[~2018-10-05 13:48 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-05  6:39 linux-next: Tree for Oct 5 Stephen Rothwell
2018-10-05 13:48 ` Guenter Roeck [this message]
2018-10-05 15:42 ` linux-next: Tree for Oct 5 (net/core/filter.c) Randy Dunlap
2018-10-05 15:51   ` Daniel Borkmann
  -- strict thread matches above, loose matches on Subject: below --
2023-10-05  3:45 linux-next: Tree for Oct 5 Stephen Rothwell
2022-10-05  7:26 Stephen Rothwell
2021-10-05  8:06 Stephen Rothwell
2016-10-05  5:14 Stephen Rothwell
2012-10-05  4:54 Stephen Rothwell
2011-10-05  8:37 Stephen Rothwell
2011-10-05 12:09 ` Valdis.Kletnieks
2011-10-05 12:36   ` Stephen Rothwell
2011-10-05 13:17     ` Valdis.Kletnieks

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=20181005134854.GA17709@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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).