From: Guenter Roeck <linux@roeck-us.net>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: Linux 4.19-rc7
Date: Sun, 7 Oct 2018 15:36:22 -0700 [thread overview]
Message-ID: <20181007223622.GA12196@roeck-us.net> (raw)
In-Reply-To: <20181007154529.GA4493@kroah.com>
On Sun, Oct 07, 2018 at 05:45:29PM +0200, Greg KH wrote:
> Hi all,
>
> Yet again, it's time for a kernel -rc release. This one is bigger than
> -rc6 was, for a variety of unrelated reasons it seems. Lots of
> different trees being merged this week, much more so than the previous
> one. Highlights include two sets of networking fixes, lots of different
> driver subsystem fixes, arm and arm64 and x86 and riscv and powerpc64
> fixes, as well as scheduler, iommu, and vfs fixes. Not a huge quantity
> overall, just overall a lot of different things.
>
> Given the current rate of change, and looking at the travel/conference
> schedule happening this month, it seems like we will be having a -rc8
> just to be sure 4.19 is solid as well as not having to be in the middle
> of a merge window during a conference week. Please go test and make
> sure any remaining problems are sent in in time.
>
Build results:
total: 135 pass: 135 fail: 0
Qemu test results:
total: 318 pass: 318 fail: 0
Details are available at https://kerneltests.org/builders/.
Notes:
- sparc32:allmodconfig is no longer built.
Starting with v4.19, nds32:allmodconfig will be built instead.
- CONFIG_OF_UNITTEST is now disabled.
Guenter
next prev parent reply other threads:[~2018-10-07 22:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-07 15:45 Linux 4.19-rc7 Greg KH
2018-10-07 22:36 ` Guenter Roeck [this message]
2018-10-08 14:28 ` Greg KH
2018-10-08 18:43 ` Shuah Khan
2018-10-09 7:14 ` Greg KH
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=20181007223622.GA12196@roeck-us.net \
--to=linux@roeck-us.net \
--cc=gregkh@linuxfoundation.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.