From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-kernel@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
torvalds@linux-foundation.org, akpm@linux-foundation.org,
linux@roeck-us.net, shuah@kernel.org, patches@kernelci.org,
ben.hutchings@codethink.co.uk, lkft-triage@lists.linaro.org,
stable@vger.kernel.org
Subject: [PATCH 4.4 0/1] 4.4.184-stable review
Date: Wed, 26 Jun 2019 16:45:04 +0800 [thread overview]
Message-ID: <20190626083604.894288021@linuxfoundation.org> (raw)
This is the start of the stable review cycle for the 4.4.184 release.
There are 1 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 Fri 28 Jun 2019 08:35:42 AM UTC.
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/v4.x/stable-review/patch-4.4.184-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-4.4.y
and the diffstat can be found below.
thanks,
greg k-h
-------------
Pseudo-Shortlog of commits:
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Linux 4.4.184-rc1
Eric Dumazet <edumazet@google.com>
tcp: refine memory limit test in tcp_fragment()
-------------
Diffstat:
Makefile | 4 ++--
net/ipv4/tcp_output.c | 2 +-
2 files changed, 3 insertions(+), 3 deletions(-)
next reply other threads:[~2019-06-26 8:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-26 8:45 Greg Kroah-Hartman [this message]
2019-06-26 8:45 ` [PATCH 4.4 1/1] tcp: refine memory limit test in tcp_fragment() Greg Kroah-Hartman
2019-06-26 17:35 ` [PATCH 4.4 0/1] 4.4.184-stable review Guenter Roeck
2019-06-26 18:41 ` Daniel Díaz
2019-06-26 21:46 ` shuah
2019-06-27 8:36 ` Jon Hunter
2019-06-27 16:54 ` Greg Kroah-Hartman
2019-06-28 8:26 ` Kelsey
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=20190626083604.894288021@linuxfoundation.org \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=ben.hutchings@codethink.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=lkft-triage@lists.linaro.org \
--cc=patches@kernelci.org \
--cc=shuah@kernel.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 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).