From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Mahesh Bandewar <maheshb@google.com>
Cc: David Miller <davem@davemloft.net>,
Netdev <netdev@vger.kernel.org>,
Eric Dumazet <edumazet@google.com>,
Mahesh Bandewar <mahesh@bandewar.net>,
Jonathan Berger <jonathann1@walla.com>,
Amit Klein <aksecurity@gmail.com>,
Benny Pinkas <benny@pinkas.net>,
Tom Herbert <tom@herbertland.com>,
stable@vger.kernel.org
Subject: Re: [PATCH v4.9-stable] net/flow_dissector: switch to siphash
Date: Thu, 7 Nov 2019 08:08:07 +0100 [thread overview]
Message-ID: <20191107070807.GA1116383@kroah.com> (raw)
In-Reply-To: <20191107040930.31289-1-maheshb@google.com>
On Wed, Nov 06, 2019 at 08:09:30PM -0800, Mahesh Bandewar wrote:
> From: Eric Dumazet <edumazet@google.com>
>
> [ Upstream commit 55667441c84fa5e0911a0aac44fb059c15ba6da2 ]
Thanks for this, and the other backports, I've queued them all up now.
greg k-h
prev parent reply other threads:[~2019-11-07 7:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-07 4:09 [PATCH v4.9-stable] net/flow_dissector: switch to siphash Mahesh Bandewar
2019-11-07 7:08 ` 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=20191107070807.GA1116383@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=aksecurity@gmail.com \
--cc=benny@pinkas.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jonathann1@walla.com \
--cc=mahesh@bandewar.net \
--cc=maheshb@google.com \
--cc=netdev@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=tom@herbertland.com \
/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).