From: Greg Kroah-Hartman <gregkh@linuxfoundation•org>
To: Peter Oskolkov <posk@google•com>
Cc: stable@vger•kernel.org, netdev@vger•kernel.org,
Peter Oskolkov <posk@posk•io>, David Miller <davem@davemloft•net>,
Eric Dumazet <edumazet@google•com>,
Sasha Levin <sashal@kernel•org>,
Captain Wiggum <captwiggum@gmail•com>,
Lars Persson <lists@bofh•nu>
Subject: Re: [PATCH 4.9 stable 0/5] net: ip6 defrag: backport fixes
Date: Tue, 30 Apr 2019 13:37:32 +0200 [thread overview]
Message-ID: <20190430113732.GA9401@kroah.com> (raw)
In-Reply-To: <20190426154108.52277-1-posk@google.com>
On Fri, Apr 26, 2019 at 08:41:03AM -0700, Peter Oskolkov wrote:
> This is a backport of a 5.1rc patchset:
> https://patchwork.ozlabs.org/cover/1029418/
>
> Which was backported into 4.19:
> https://patchwork.ozlabs.org/cover/1081619/
>
> and into 4.14:
> https://patchwork.ozlabs.org/cover/1089651/
>
>
> This 4.9 patchset is very close to the 4.14 patchset above
> (cherry-picks from 4.14 were almost clean).
>
All now queued up, thanks!
greg k-h
prev parent reply other threads:[~2019-04-30 11:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-26 15:41 [PATCH 4.9 stable 0/5] net: ip6 defrag: backport fixes Peter Oskolkov
2019-04-26 15:41 ` [PATCH 4.9 stable 1/5] ipv6: frags: fix a lockdep false positive Peter Oskolkov
2019-04-26 15:41 ` [PATCH 4.9 stable 2/5] net: IP defrag: encapsulate rbtree defrag code into callable functions Peter Oskolkov
2019-04-26 15:41 ` [PATCH 4.9 stable 3/5] ipv6: remove dependency of nf_defrag_ipv6 on ipv6 module Peter Oskolkov
2019-04-26 15:41 ` [PATCH 4.9 stable 4/5] net: IP6 defrag: use rbtrees for IPv6 defrag Peter Oskolkov
2019-04-26 15:41 ` [PATCH 4.9 stable 5/5] net: IP6 defrag: use rbtrees in nf_conntrack_reasm.c Peter Oskolkov
2019-04-26 21:26 ` [PATCH 4.9 stable 0/5] net: ip6 defrag: backport fixes Peter Oskolkov
2019-04-29 16:54 ` Captain Wiggum
2019-04-27 1:02 ` Captain Wiggum
2019-04-29 16:57 ` Captain Wiggum
2019-04-29 17:23 ` Captain Wiggum
2019-04-29 17:31 ` Peter Oskolkov
2019-04-30 11:37 ` Greg Kroah-Hartman [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=20190430113732.GA9401@kroah.com \
--to=gregkh@linuxfoundation$(echo .)org \
--cc=captwiggum@gmail$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=edumazet@google$(echo .)com \
--cc=lists@bofh$(echo .)nu \
--cc=netdev@vger$(echo .)kernel.org \
--cc=posk@google$(echo .)com \
--cc=posk@posk$(echo .)io \
--cc=sashal@kernel$(echo .)org \
--cc=stable@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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