From: patchwork-bot+netdevbpf@kernel.org
To: =?utf-8?b?QXNiasO4cm4gU2xvdGggVMO4bm5lc2VuIDxhc3RAZmliZXJieS5uZXQ+?=@ci.codeaurora.org
Cc: netdev@vger.kernel.org, dcaratti@redhat.com, i.maximets@ovn.org,
jhs@mojatatu.com, xiyou.wangcong@gmail.com, jiri@resnulli.us,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, dsahern@kernel.org, horms@kernel.org,
rkannoth@marvell.com, fw@strlen.de, aleksander.lobakin@intel.com,
donald.hunter@gmail.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v4 00/13] flower: rework TCA_FLOWER_KEY_ENC_FLAGS usage
Date: Mon, 15 Jul 2024 16:40:35 +0000 [thread overview]
Message-ID: <172106163520.24349.6809733629118549125.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240713021911.1631517-1-ast@fiberby.net>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Sat, 13 Jul 2024 02:18:57 +0000 you wrote:
> This series reworks the recently added TCA_FLOWER_KEY_ENC_FLAGS
> attribute, to be more like TCA_FLOWER_KEY_FLAGS, and use the unused
> u32 flags field in FLOW_DISSECTOR_KEY_ENC_CONTROL, instead of adding
> a new flags field as FLOW_DISSECTOR_KEY_ENC_FLAGS.
>
> I have defined the new FLOW_DIS_F_* and TCA_FLOWER_KEY_FLAGS_*
> flags to co-exist with the existing flags, so the meaning
> of the flags field in struct flow_dissector_key_control is not
> depending on the context it is used in. If we run out of bits
> then we can always split them up later, if we really want to.
> Future flags might also be valid in both contexts.
>
> [...]
Here is the summary with links:
- [net-next,v4,01/13] net/sched: flower: refactor control flag definitions
https://git.kernel.org/netdev/net-next/c/6e5c85c003e4
- [net-next,v4,02/13] doc: netlink: specs: tc: describe flower control flags
https://git.kernel.org/netdev/net-next/c/49ba9fc1c773
- [net-next,v4,03/13] net/sched: flower: define new tunnel flags
https://git.kernel.org/netdev/net-next/c/bfda5a63137b
- [net-next,v4,04/13] net/sched: cls_flower: prepare fl_{set,dump}_key_flags() for ENC_FLAGS
https://git.kernel.org/netdev/net-next/c/fcb4bb07a927
- [net-next,v4,05/13] net/sched: cls_flower: add policy for TCA_FLOWER_KEY_FLAGS
https://git.kernel.org/netdev/net-next/c/0e83a7875d69
- [net-next,v4,06/13] flow_dissector: prepare for encapsulated control flags
https://git.kernel.org/netdev/net-next/c/4d0aed380f9d
- [net-next,v4,07/13] flow_dissector: set encapsulated control flags from tun_flags
https://git.kernel.org/netdev/net-next/c/03afeb613bfe
- [net-next,v4,08/13] net/sched: cls_flower: add tunnel flags to fl_{set,dump}_key_flags()
https://git.kernel.org/netdev/net-next/c/988f8723d398
- [net-next,v4,09/13] net/sched: cls_flower: rework TCA_FLOWER_KEY_ENC_FLAGS usage
https://git.kernel.org/netdev/net-next/c/11036bd7a0b3
- [net-next,v4,10/13] doc: netlink: specs: tc: flower: add enc-flags
https://git.kernel.org/netdev/net-next/c/880a51a8ab8c
- [net-next,v4,11/13] flow_dissector: cleanup FLOW_DISSECTOR_KEY_ENC_FLAGS
https://git.kernel.org/netdev/net-next/c/db5271d50ec1
- [net-next,v4,12/13] flow_dissector: set encapsulation control flags for non-IP
https://git.kernel.org/netdev/net-next/c/706bf4f44c6d
- [net-next,v4,13/13] net/sched: cls_flower: propagate tca[TCA_OPTIONS] to NL_REQ_ATTR_CHECK
https://git.kernel.org/netdev/net-next/c/536b97acddd7
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2024-07-15 16:40 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-13 2:18 Asbjørn Sloth Tønnesen
2024-07-13 2:18 ` [PATCH net-next v4 01/13] net/sched: flower: refactor control flag definitions Asbjørn Sloth Tønnesen
2024-07-13 2:18 ` [PATCH net-next v4 02/13] doc: netlink: specs: tc: describe flower control flags Asbjørn Sloth Tønnesen
2024-07-13 13:16 ` Donald Hunter
2024-07-13 2:19 ` [PATCH net-next v4 03/13] net/sched: flower: define new tunnel flags Asbjørn Sloth Tønnesen
2024-07-13 13:19 ` Donald Hunter
2024-07-13 2:19 ` [PATCH net-next v4 04/13] net/sched: cls_flower: prepare fl_{set,dump}_key_flags() for ENC_FLAGS Asbjørn Sloth Tønnesen
2024-07-13 2:19 ` [PATCH net-next v4 05/13] net/sched: cls_flower: add policy for TCA_FLOWER_KEY_FLAGS Asbjørn Sloth Tønnesen
2024-07-13 2:19 ` [PATCH net-next v4 06/13] flow_dissector: prepare for encapsulated control flags Asbjørn Sloth Tønnesen
2024-07-13 2:19 ` [PATCH net-next v4 07/13] flow_dissector: set encapsulated control flags from tun_flags Asbjørn Sloth Tønnesen
2024-07-13 2:19 ` [PATCH net-next v4 08/13] net/sched: cls_flower: add tunnel flags to fl_{set,dump}_key_flags() Asbjørn Sloth Tønnesen
2024-07-13 2:19 ` [PATCH net-next v4 09/13] net/sched: cls_flower: rework TCA_FLOWER_KEY_ENC_FLAGS usage Asbjørn Sloth Tønnesen
2024-07-13 2:19 ` [PATCH net-next v4 10/13] doc: netlink: specs: tc: flower: add enc-flags Asbjørn Sloth Tønnesen
2024-07-13 13:21 ` Donald Hunter
2024-07-13 2:19 ` [PATCH net-next v4 11/13] flow_dissector: cleanup FLOW_DISSECTOR_KEY_ENC_FLAGS Asbjørn Sloth Tønnesen
2024-07-13 2:19 ` [PATCH net-next v4 12/13] flow_dissector: set encapsulation control flags for non-IP Asbjørn Sloth Tønnesen
2024-07-13 2:19 ` [PATCH net-next v4 13/13] net/sched: cls_flower: propagate tca[TCA_OPTIONS] to NL_REQ_ATTR_CHECK Asbjørn Sloth Tønnesen
2024-07-15 16:40 ` patchwork-bot+netdevbpf [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=172106163520.24349.6809733629118549125.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc==?utf-8?b?QXNiasO4cm4gU2xvdGggVMO4bm5lc2VuIDxhc3RAZmliZXJieS5uZXQ+?=@ci.codeaurora.org \
--cc=aleksander.lobakin@intel.com \
--cc=davem@davemloft.net \
--cc=dcaratti@redhat.com \
--cc=donald.hunter@gmail.com \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=fw@strlen.de \
--cc=horms@kernel.org \
--cc=i.maximets@ovn.org \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rkannoth@marvell.com \
--cc=xiyou.wangcong@gmail.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
all inboxes | Powered by JetHome®