From: Philip Prindeville <philipp@redfish-solutions.com>
To: Feng Gao <gfree.wind@gmail.com>
Cc: Tom Herbert <tom@herbertland.com>,
Gao Feng <fgao@48lvckh6395k16k5.yundunddos.com>,
"David S. Miller" <davem@davemloft.net>,
Stephen Hemminger <stephen@networkplumber.org>,
Pravin B Shelar <pshelar@nicira.com>,
Alex Duyck <aduyck@mirantis.com>,
Linux Kernel Network Developers <netdev@vger.kernel.org>
Subject: Re: [PATCH 1/1] rps: Inspect PPTP encapsulated by GRE to get flow hash
Date: Tue, 2 Aug 2016 19:11:18 -0600 [thread overview]
Message-ID: <2AC57BFE-E95C-4690-BE9F-4A1B6DB44893@redfish-solutions.com> (raw)
In-Reply-To: <CA+6hz4qVM=bS_8fHx2HogHObbRsVpoRqLrk51FTPcbX38j2yxg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 216 bytes --]
In this case they both mean the same thing.
> On Aug 2, 2016, at 6:28 PM, Feng Gao <gfree.wind@gmail.com> wrote:
>
> Just a reminder, the version description is "contain 1", not "set 1".
>
> Best Regards
> Feng
[-- Attachment #2: Message signed with OpenPGP using GPGMail --]
[-- Type: application/pgp-signature, Size: 496 bytes --]
next prev parent reply other threads:[~2016-08-03 1:13 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-28 7:14 [PATCH 1/1] rps: Inspect PPTP encapsulated by GRE to get flow hash fgao
2016-08-02 1:36 ` Philp Prindeville
2016-08-02 6:10 ` Feng Gao
2016-08-02 17:33 ` Philp Prindeville
2016-08-03 0:22 ` Feng Gao
2016-08-02 20:35 ` Tom Herbert
2016-08-03 0:28 ` Feng Gao
2016-08-03 1:11 ` Philip Prindeville [this message]
2016-08-03 1:59 ` Tom Herbert
2016-08-03 2:17 ` Feng Gao
2016-08-03 4:01 ` Tom Herbert
2016-08-03 15:02 ` Feng Gao
-- strict thread matches above, loose matches on Subject: below --
2016-07-27 23:42 fgao
2016-07-28 0:04 ` Tom Herbert
2016-07-28 0:24 ` Feng Gao
2016-07-28 0:35 ` Feng Gao
2016-07-28 0:46 ` Philp Prindeville
2016-08-01 7:36 ` Feng Gao
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=2AC57BFE-E95C-4690-BE9F-4A1B6DB44893@redfish-solutions.com \
--to=philipp@redfish-solutions.com \
--cc=aduyck@mirantis.com \
--cc=davem@davemloft.net \
--cc=fgao@48lvckh6395k16k5.yundunddos.com \
--cc=gfree.wind@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pshelar@nicira.com \
--cc=stephen@networkplumber.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 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.