From: David Ahern <dsahern@gmail.com>
To: Xin Long <lucien.xin@gmail.com>,
Jakub Kicinski <jakub.kicinski@netronome.com>
Cc: network dev <netdev@vger.kernel.org>, davem <davem@davemloft.net>,
Simon Horman <simon.horman@netronome.com>
Subject: Re: [PATCH net-next 1/4] net: sched: add vxlan option support to act_tunnel_key
Date: Thu, 21 Nov 2019 08:56:36 -0700 [thread overview]
Message-ID: <c9e37f21-163b-0c0f-4b39-741573a11664@gmail.com> (raw)
In-Reply-To: <CADvbK_dbT5XTtUvu6qhk8JvH3UQYJN8bOPMTqmvi3mCEn+Yt1g@mail.gmail.com>
On 11/20/19 10:45 PM, Xin Long wrote:
>> Hm, that's what I thought but then we were asked to add it in
>> act_mpls.c. I should've checked the code.
>>
>> Anyway, we should probably clean up act_mpls.c and act_ct.c so people
>> don't copy it unnecessarily.
> will send a cleanup, also for the one in net/ipv4/nexthop.c.
thanks. Clearly, I forgot .strict_type_start does not apply to users of
the new API.
next prev parent reply other threads:[~2019-11-21 15:56 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-19 9:31 [PATCH net-next 0/4] net: sched: support vxlan and erspan options Xin Long
2019-11-19 9:31 ` [PATCH net-next 1/4] net: sched: add vxlan option support to act_tunnel_key Xin Long
2019-11-19 9:31 ` [PATCH net-next 2/4] net: sched: add erspan " Xin Long
2019-11-19 9:31 ` [PATCH net-next 3/4] net: sched: allow flower to match vxlan options Xin Long
2019-11-19 9:31 ` [PATCH net-next 4/4] net: sched: allow flower to match erspan options Xin Long
2019-11-20 0:27 ` [PATCH net-next 2/4] net: sched: add erspan option support to act_tunnel_key Jakub Kicinski
2019-11-20 5:15 ` Xin Long
2019-11-20 0:12 ` [PATCH net-next 1/4] net: sched: add vxlan " Jakub Kicinski
2019-11-20 5:08 ` Xin Long
2019-11-20 17:17 ` Jakub Kicinski
2019-11-21 5:45 ` Xin Long
2019-11-21 15:56 ` David Ahern [this message]
2019-11-19 14:18 ` [PATCH net-next 0/4] net: sched: support vxlan and erspan options Roman Mashak
2019-11-19 15:55 ` Xin Long
2019-11-19 16:06 ` Roman Mashak
2019-11-19 16:23 ` Xin Long
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=c9e37f21-163b-0c0f-4b39-741573a11664@gmail.com \
--to=dsahern@gmail.com \
--cc=davem@davemloft.net \
--cc=jakub.kicinski@netronome.com \
--cc=lucien.xin@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=simon.horman@netronome.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).