From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932928AbbD0Mva (ORCPT ); Mon, 27 Apr 2015 08:51:30 -0400 Received: from bh-25.webhostbox.net ([208.91.199.152]:40334 "EHLO bh-25.webhostbox.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932893AbbD0Mv1 (ORCPT ); Mon, 27 Apr 2015 08:51:27 -0400 Date: Mon, 27 Apr 2015 05:51:22 -0700 From: Guenter Roeck To: Linus Torvalds Cc: Linux Kernel Mailing List Subject: Re: Linux 4.1-rc1 Message-ID: <20150427125122.GA13489@roeck-us.net> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) X-Authenticated_sender: guenter@roeck-us.net X-OutGoing-Spam-Status: No, score=-1.0 X-CTCH-PVer: 0000001 X-CTCH-Spam: Unknown X-CTCH-VOD: Unknown X-CTCH-Flags: 0 X-CTCH-RefID: str=0001.0A020205.553E30CE.0326,ss=1,re=0.000,recu=0.000,reip=0.000,cl=1,cld=1,fgs=0 X-CTCH-Score: 0.000 X-CTCH-ScoreCust: 0.000 X-CTCH-Rules: X-CTCH-SenderID: linux@roeck-us.net X-CTCH-SenderID-Flags: 0 X-CTCH-SenderID-TotalMessages: 2 X-CTCH-SenderID-TotalSpam: 0 X-CTCH-SenderID-TotalSuspected: 0 X-CTCH-SenderID-TotalConfirmed: 0 X-CTCH-SenderID-TotalBulk: 0 X-CTCH-SenderID-TotalVirus: 0 X-CTCH-SenderID-TotalRecipients: 0 X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - bh-25.webhostbox.net X-AntiAbuse: Original Domain - vger.kernel.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - roeck-us.net X-Get-Message-Sender-Via: bh-25.webhostbox.net: mailgid no entry from get_relayhosts_entry X-Source: X-Source-Args: X-Source-Dir: Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sun, Apr 26, 2015 at 06:32:25PM -0700, Linus Torvalds wrote: > It's been a normal merge window, and I'm releasing according to the > normal schedule. The few days of travel didn't seem to matter, as I > had internet access at all times. > > The merge window is pretty normal in terms of what got merged too. > Just eyeballing the size, it looks like this is going to fit right in > - while 4.0 was a bit smaller than usual, 4.1 seems to be smack dab in > the middle of the normal range for the last couple of years. And all > the patch statistics look normal as well: the bulk of the changes are > to drivers (just under 60% of the patch), with arch updates being > about 20% of it all, and the rest is spread all over. > > No earth-shattering new features come to mind, even if initial support > for ACPI on arm64 looks funny. Depending on what you care about, your > notion of "big new feature" may differ from mine, of course. There's a > lot of work all over, and some of it might just make a big difference > to your use cases. > > So go out and test. Even -rc1, as raw as it may sometimes be, has > tended to be pretty good. It's not that scary. Promise. > Build results: total: 123 pass: 115 fail: 8 Failed builds: m68k:allmodconfig mips:allmodconfig mips:nlm_xlp_defconfig mips:cavium_octeon_defconfig mips:malta_defconfig s390:allmodconfig score:defconfig xtensa:allmodconfig Qemu test results: total: 30 pass: 27 fail: 3 Failed tests: mips:mips_malta_smp_defconfig mips:mipsel_malta_smp_defconfig mips64:mips_malta64_smp_defconfig Good news is that there are patches waiting to be applied which fix all the above build problems. score: Fix exception handler label [1] xtensa: Provide dummy dma_alloc_attrs() and dma_free_attrs() [2] mips: Fix SMP builds [3] spi: bcm2835: Add GPIOLIB dependency [4] Guenter --- [1] https://patchwork.kernel.org/patch/6221401/ [2] https://patchwork.kernel.org/patch/6252861/ [3] https://patchwork.kernel.org/patch/6250441/ [4] https://patchwork.kernel.org/patch/6213711/