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>,
	Trond Myklebust <trond.myklebust@hammerspace.com>,
	"J. Bruce Fields" <bfields@redhat.com>
Subject: Re: linux-next: Tree for Apr 9
Date: Tue, 9 Apr 2019 11:25:24 -0700	[thread overview]
Message-ID: <20190409182524.GA18518@roeck-us.net> (raw)
In-Reply-To: <20190409180042.15bb90b6@canb.auug.org.au>

On Tue, Apr 09, 2019 at 06:00:42PM +1000, Stephen Rothwell wrote:
> Hi all,
> 
> Changes since 20190408:
> 
> The mac80211-next tree gained a conflict against the mac80211 tree.
> 
> The drm tree still had its build failure for which I disabled a driver.
> 
> The drm-misc tree gained conflicts against the drm tree and also a build
> failure for which I marked a driver as BROKEN.
> 
> The scsi-mkp tree gained a build failure for which I reverted a commit.
> 
> The rtc tree gained a conflict against the omap tree.
> 
> Non-merge commits (relative to Linus' tree): 5587
>  5386 files changed, 176906 insertions(+), 87493 deletions(-)
> 

This one deserves a reply.

Build results:
	total: 159 pass: 144 fail: 15
Failed builds: 
	<many>
Qemu test results:
	total: 345 pass: 227 fail: 118
Failed tests: 
	<many>

Build failure is:

s/nfsd/nfssvc.c: In function 'nfsd_support_acl_version':
fs/nfsd/nfssvc.c:145:14: error: 'NFSD_ACL_MINVERS' undeclared

and similar. Build failures and (many ? most ? all ?) of the qemu failures
are due to commit 55d4c716ea ("nfsd: Add custom rpcbind callbacks for
knfsd").

Guenter

  parent reply	other threads:[~2019-04-09 18:25 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-09  8:00 linux-next: Tree for Apr 9 Stephen Rothwell
2019-04-09 15:21 ` linux-next: Tree for Apr 9 (spi/spi-zynq-qspi.c) Randy Dunlap
2019-04-10  5:46   ` Naga Sureshkumar Relli
2019-04-09 15:28 ` linux-next: Tree for Apr 9 (arch/x86/platform/efi/efi_64.c) Randy Dunlap
2019-04-09 18:25 ` Guenter Roeck [this message]
2019-04-09 18:44   ` linux-next: Tree for Apr 9 Trond Myklebust
  -- strict thread matches above, loose matches on Subject: below --
2024-04-09  4:50 Stephen Rothwell
2021-04-09 11:51 Stephen Rothwell
2020-04-09  5:10 Stephen Rothwell
2018-04-09  4:42 Stephen Rothwell
2015-04-09  9:31 Stephen Rothwell
2014-04-09  7:22 Stephen Rothwell
2013-04-09 10:56 Sedat Dilek
2013-04-09 12:37 ` Sedat Dilek
2013-04-09 13:34   ` Sedat Dilek
2013-04-09 13:59 ` Stephen Rothwell
2013-04-09 14:03   ` Sedat Dilek
2013-04-09 14:11   ` Sedat Dilek
2013-04-09 14:23     ` Stephen Rothwell
2013-04-09 14:32       ` Sedat Dilek
2013-04-09 15:11         ` Sedat Dilek
2013-04-09 15:48           ` Sedat Dilek
2013-04-09  9:30 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=20190409182524.GA18518@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=bfields@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --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).