Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Date:   Mon, 3 Sep 2018 11:22:02 -0700
From:   Guenter Roeck <linux@roeck-us.net>
To:     Linus Torvalds <torvalds@linux-foundation.org>
Cc:     Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
        "David S. Miller" <davem@davemloft.net>
Subject: Re: Linux 4.19-rc2
Message-ID: <20180903182202.GA14258@roeck-us.net>
References: <CA+55aFyG0GbDfoghEhAmKBPcZCiPu6CCpPRz9GwjCzLuP_Vv5Q@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CA+55aFyG0GbDfoghEhAmKBPcZCiPu6CCpPRz9GwjCzLuP_Vv5Q@mail.gmail.com>
User-Agent: Mutt/1.5.24 (2015-08-30)
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

On Sun, Sep 02, 2018 at 02:45:22PM -0700, Linus Torvalds wrote:
> As usual, the rc2 release is pretty small. People are taking a
> breather after the merge window, and it takes a bit of time for bug
> reports to start coming in and get identified.  Plus people were
> probably still on vacation (particularly Europe), and some people were
> at Open Source Summit NA last week too. Having a calm week was good.
> 
> Regardless of the reason, it's pretty quiet/ The bulk of it is drivers
> (network and gpu stand out), with the rest being a random collection
> all over (arch/x86 and generic networking stands out, but there's misc
> stuff all over).
> 
> Go out and test.
> 

Build results:
	total: 134 pass: 133 fail: 1
Failed builds: 
	sparc32:allmodconfig 
Qemu test results:
	total: 302 pass: 301 fail: 1
Failed tests: 
	riscv:virt:defconfig:initrd

The sparc32:allmodconfig build problem is the same as last week.
David - any interest/plan to get this fixed, or should I just drop
the build ?

The riscv:virt:defconfig:initrd boot test is known to fail. The patch
fixing it is in -next.

---
Runtime warnings:

arm:

WARNING: CPU: 0 PID: 1 at ./include/linux/dma-mapping.h:516 drm_gem_cma_create+0x13c/0x158

This is seen now due to a newly enabled configuration option.
Fix is in -next.

---
sh4:

WARNING: CPU: 0 PID: 932 at mm/slab.c:2666 cache_alloc_refill+0x8a/0x594

Same as before. I'll try to dig up the patch and ask for the status.

---
sparc32:

WARNING: CPU: 0 PID: 1 at ./include/linux/dma-mapping.h:516 esp_sbus_probe+0x408/0x6e8
WARNING: CPU: 0 PID: 1 at ./include/linux/dma-mapping.h:516 sparc_lance_probe_one+0x428/0x4f4

Fix is in -next.

Detailed logs are available at https://kerneltests.org/builders/.

Guenter