From: Guenter Roeck <linux@roeck-us.net>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 4.18-rc6
Date: Mon, 23 Jul 2018 13:46:17 -0700 [thread overview]
Message-ID: <20180723204617.GA14487@roeck-us.net> (raw)
In-Reply-To: <CA+55aFzMheDA-2z=MdGgJrz-REcrknb+4OEvRKaJipm+x6xEhw@mail.gmail.com>
On Sun, Jul 22, 2018 at 02:23:39PM -0700, Linus Torvalds wrote:
> So this was the week when the other shoe dropped ... The reason the
> two previous rc releases were so nice and small was that David hadn't
> sent me much networking fixes, and they came in this week.
>
Build results:
total: 134 pass: 133 fail: 1
Failed builds:
sparc32:allmodconfig
Qemu test results:
total: 172 pass: 172 fail: 0
The s390 gcc plugins related build error reported previously has not really
been fixed; after feedback from the s390 maintainers, suggesting that it
won't get fixed in 4.18, I disabled GCC_PLUGINS for s390 builds. This is
not my preferred solution, but it beats not testing s390:allmodconfig
builds at all.
The sparc32 build error is still:
In file included from
...
from drivers/staging/media/omap4iss/iss_video.c:15:
include/linux/highmem.h: In function 'clear_user_highpage':
include/linux/highmem.h:137:31: error:
passing argument 1 of 'sparc_flush_page_to_ram' from incompatible pointer type
due to a missing declaration of 'struct page', as previously reported.
Guenter
next prev parent reply other threads:[~2018-07-23 20:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-22 21:23 Linux 4.18-rc6 Linus Torvalds
2018-07-23 20:46 ` Guenter Roeck [this message]
2018-07-23 20:56 ` Linus Torvalds
2018-07-23 21:06 ` David Miller
2018-07-23 21:23 ` Guenter Roeck
2018-07-23 23:16 ` Linus Torvalds
2018-07-23 23:17 ` Linus Torvalds
2018-07-24 6:18 ` Martin Schwidefsky
2018-07-24 7:15 ` Christian Borntraeger
2018-07-24 7:24 ` Martin Schwidefsky
2018-07-24 7:28 ` Christian Borntraeger
2018-07-25 19:40 ` Kees Cook
2018-07-26 6:00 ` Martin Schwidefsky
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=20180723204617.GA14487@roeck-us.net \
--to=linux@roeck-us.net \
--cc=linux-kernel@vger.kernel.org \
--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