From: Guenter Roeck <linux@roeck-us.net>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Mikael Starvik <starvik@axis.com>,
Jesper Nilsson <jesper.nilsson@axis.com>,
linux-cris-kernel@axis.com, linux-serial@vger.kernel.org
Subject: Re: Linux 4.4-rc1
Date: Sun, 15 Nov 2015 21:27:56 -0800 [thread overview]
Message-ID: <20151116052756.GA1546@roeck-us.net> (raw)
In-Reply-To: <CA+55aFz8NHGxf0cvgQOVAmB=i+g+egty_j6nMYc1YBv4tXAvxg@mail.gmail.com>
On Sun, Nov 15, 2015 at 05:24:37PM -0800, Linus Torvalds wrote:
> So it's Sunday, two weeks has passed, and so 4.4-rc1 is out there and
> the merge window is closed.
>
> As usual, the full shortlog is much too big to post, so appended is
> the usual shortlog of just my merges, which just shows who I did pulls
> from, with a very short comment on each merge.
>
> Just looking at the patch itself, things look fairly normal at a high
> level, possibly a bit more driver-heavy than usual with about 75% of
> the patch being drivers, and 10% being architecture updates. The
> remaining 15% is documentation, filesystem, core networking (as
> opposed to network drivers), tooling and some core infrastructure.
>
> The driver changes are all over, although staging, networking and GPU
> drivers stand out (and those three areas account for over half of the
> driver changes - roughly 40% of the whole patch).
>
> On the architecture side, ARM (when counting both 32-bit and 64-bit)
> accounts for about half the changes, with x86, powerpc, mips, chris
> and s390 accounting for the other half.
>
> Go out and test.
>
Build results:
total: 144 pass: 143 fail: 1
Failed builds:
cris:allnoconfig
Qemu test results:
total: 95 pass: 94 fail: 1
Failed tests:
cris:crisv32_defconfig
cris:allnoconfig fails to build because of section mismatches, which is now
fatal with allnoconfig builds (since 47490ec141b9, "modpost: Add flag -E for
making section mismatches fatal"). Proposed patches to fix the problems are
available at [1] and [2]. Other allnoconfig builds (untested by me) probably
fail as well, though.
The cris:crisv32_defconfig qemu test crashes because of interference between
commit 7d8c70d8048c ("serial: mctrl-gpio: rename init function") and commit
7b9c5162c182 ("serial: etraxfs-uart: use mctrl_gpio helpers for handling
modem signals"). A proposed patch is available at [3].
Further details are available at http://server.roeck-us.net:8010/builders.
Guenter
---
[1] https://patchwork.kernel.org/patch/7592471/
[2] https://patchwork.kernel.org/patch/7592461/
[3] https://patchwork.kernel.org/patch/7533041/
next prev parent reply other threads:[~2015-11-16 5:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-16 1:24 Linus Torvalds
2015-11-16 4:51 ` Ken Moffat
2015-11-16 5:27 ` Guenter Roeck [this message]
2015-11-18 14:46 ` Shuah Khan
2015-11-18 16:17 ` Linus Torvalds
2015-11-18 17:12 ` David Miller
2015-11-19 14:10 ` Shuah Khan
2015-11-19 19:25 ` Linus Torvalds
2015-11-20 1:39 ` Shuah Khan
2015-11-19 4:45 ` linux-next: stats for v4.4-rc1 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=20151116052756.GA1546@roeck-us.net \
--to=linux@roeck-us.net \
--cc=gregkh@linuxfoundation.org \
--cc=jesper.nilsson@axis.com \
--cc=linux-cris-kernel@axis.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=starvik@axis.com \
--cc=torvalds@linux-foundation.org \
/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
all inboxes | Powered by JetHome®