From: Willy Tarreau <w@1wt.eu>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org, torvalds@linux-foundation.org,
akpm@linux-foundation.org, linux@roeck-us.net,
shuah.kh@samsung.com, patches@kernelci.org,
ben.hutchings@codethink.co.uk, stable@vger.kernel.org
Subject: Re: [PATCH 4.4 0/2] 4.4.30-stable review
Date: Mon, 31 Oct 2016 19:34:49 +0100 [thread overview]
Message-ID: <20161031183449.GA17564@1wt.eu> (raw)
In-Reply-To: <20161031175027.498906529@linuxfoundation.org>
On Mon, Oct 31, 2016 at 11:52:49AM -0600, Greg Kroah-Hartman wrote:
> Based on the discussion at the kernel summit a few hours ago, here's a
> quick bug-fix release for 4.4-stable to resolve an issue with 4.4.29 and
> older kernels. I'll probably release it once the testing systems run on
> it to verify nothing is broken.
>
> This is the start of the stable review cycle for the 4.4.30 release.
> There are 2 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Responses should be made as soon as possible!
FWIW I've just booted it in an x86_64 VM here and didn't notice anything
wrong.
Willy
next prev parent reply other threads:[~2016-10-31 18:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-31 17:52 [PATCH 4.4 0/2] 4.4.30-stable review Greg Kroah-Hartman
2016-10-31 17:52 ` [PATCH 4.4 1/2] [PATCH 1/2] Revert "x86/mm: Expand the exception table logic to allow new handling options" Greg Kroah-Hartman
2016-10-31 17:52 ` [PATCH 4.4 2/2] [PATCH 2/2] Revert "fix minor infoleak in get_user_ex()" Greg Kroah-Hartman
2016-10-31 18:34 ` Willy Tarreau [this message]
2016-10-31 21:33 ` [PATCH 4.4 0/2] 4.4.30-stable review Greg Kroah-Hartman
2016-10-31 20:49 ` Guenter Roeck
2016-10-31 21:33 ` Greg Kroah-Hartman
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=20161031183449.GA17564@1wt.eu \
--to=w@1wt.eu \
--cc=akpm@linux-foundation.org \
--cc=ben.hutchings@codethink.co.uk \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=patches@kernelci.org \
--cc=shuah.kh@samsung.com \
--cc=stable@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;
as well as URLs for NNTP newsgroup(s).