From: shuah <shuah@kernel.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org
Cc: torvalds@linux-foundation.org, akpm@linux-foundation.org,
linux@roeck-us.net, patches@kernelci.org,
ben.hutchings@codethink.co.uk, lkft-triage@lists.linaro.org,
stable@vger.kernel.org, shuah <shuah@kernel.org>
Subject: Re: [PATCH 5.3 0/6] 5.3.13-stable review
Date: Fri, 22 Nov 2019 13:45:05 -0700 [thread overview]
Message-ID: <30001ff5-2c8b-49e4-bc41-a43e0284df2c@kernel.org> (raw)
In-Reply-To: <20191122100320.878809004@linuxfoundation.org>
On 11/22/19 3:30 AM, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 5.3.13 release.
> There are 6 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 by Sun, 24 Nov 2019 09:59:19 +0000.
> Anything received after that time might be too late.
>
> The whole patch series can be found in one patch at:
> https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/patch-5.3.13-rc1.gz
> or in the git tree and branch at:
> git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-5.3.y
> and the diffstat can be found below.
>
> thanks,
>
> greg k-h
>
Compiled and booted on my test system. No dmesg regressions.
thanks,
-- Shuah
next prev parent reply other threads:[~2019-11-22 20:45 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-22 10:30 [PATCH 5.3 0/6] 5.3.13-stable review Greg Kroah-Hartman
2019-11-22 10:30 ` [PATCH 5.3 1/6] net: cdc_ncm: Signedness bug in cdc_ncm_set_dgram_size() Greg Kroah-Hartman
2019-11-22 10:30 ` [PATCH 5.3 2/6] block, bfq: deschedule empty bfq_queues not referred by any process Greg Kroah-Hartman
2019-11-22 10:30 ` [PATCH 5.3 4/6] mm/memory_hotplug: fix updating the node span Greg Kroah-Hartman
2019-11-22 10:30 ` [PATCH 5.3 5/6] arm64: uaccess: Ensure PAN is re-enabled after unhandled uaccess fault Greg Kroah-Hartman
2019-11-22 10:30 ` [PATCH 5.3 6/6] fbdev: Ditch fb_edid_add_monspecs Greg Kroah-Hartman
2019-11-22 13:39 ` [PATCH 5.3 0/6] 5.3.13-stable review Jon Hunter
2019-11-22 13:39 ` Jon Hunter
2019-11-22 13:46 ` Greg Kroah-Hartman
2019-11-22 18:14 ` Guenter Roeck
2019-11-24 7:00 ` Greg Kroah-Hartman
2019-11-22 20:45 ` shuah [this message]
2019-11-23 17:36 ` Greg Kroah-Hartman
2019-11-22 23:50 ` Daniel Díaz
2019-11-23 17:29 ` 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=30001ff5-2c8b-49e4-bc41-a43e0284df2c@kernel.org \
--to=shuah@kernel.org \
--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=lkft-triage@lists.linaro.org \
--cc=patches@kernelci.org \
--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 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.