From: Kelsey <skunberg.kelsey@gmail.com>
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@kernel.org,
patches@kernelci.org, ben.hutchings@codethink.co.uk,
lkft-triage@lists.linaro.org, stable@vger.kernel.org
Subject: Re: [PATCH 4.4 0/1] 4.4.184-stable review
Date: Fri, 28 Jun 2019 02:26:40 -0600 [thread overview]
Message-ID: <28E380A7-7D7D-49DC-B100-459F43C0FC01@gmail.com> (raw)
In-Reply-To: <20190626083604.894288021@linuxfoundation.org>
Compiled, booted, and no dmesg regressions on my system.
Cheers,
Kelsey
> On Jun 26, 2019, at 2:45 AM, Greg Kroah-Hartman <gregkh@linuxfoundation.org> wrote:
>
> 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(-)
>
>
prev parent reply other threads:[~2019-06-28 8:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-26 8:45 Greg Kroah-Hartman
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 [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=28E380A7-7D7D-49DC-B100-459F43C0FC01@gmail.com \
--to=skunberg.kelsey@gmail.com \
--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=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
all inboxes | Powered by JetHome®