From: Greg KH <gregkh@linuxfoundation.org>
To: Shuah Khan <shuahkhan@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
shuah@kernel.org
Subject: Re: Linux 4.19-rc7
Date: Tue, 9 Oct 2018 09:14:25 +0200 [thread overview]
Message-ID: <20181009071425.GD8617@kroah.com> (raw)
In-Reply-To: <CAKocOOOY7tmTt1JVv2NuF_KxGKj43MsEnEt9bH2P0EzQh7f++A@mail.gmail.com>
On Mon, Oct 08, 2018 at 12:43:05PM -0600, Shuah Khan wrote:
> On Sun, Oct 7, 2018 at 9:48 AM Greg KH <gregkh@linuxfoundation.org> 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.
> >
> > thanks,
> >
> > greg k-h
> >
> Compiled and booted on my test system. I haven't seen any new issues compared
> to 4.19-rc6
Great!
prev parent reply other threads:[~2018-10-09 7:14 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
2018-10-08 14:28 ` Greg KH
2018-10-08 18:43 ` Shuah Khan
2018-10-09 7:14 ` Greg KH [this message]
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=20181009071425.GD8617@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=shuah@kernel.org \
--cc=shuahkhan@gmail.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