From: patchwork-bot+netdevbpf@kernel.org
To: Xuesen Huang <hxseverything@gmail.com>
Cc: daniel@iogearbox.net, davem@davemloft.net, bpf@vger.kernel.org,
willemdebruijn.kernel@gmail.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, xiyou.wangcong@gmail.com,
huangxuesen@kuaishou.com, willemb@google.com,
chengzhiyong@kuaishou.com, wangli09@kuaishou.com
Subject: Re: [PATCH/v5] bpf: add bpf_skb_adjust_room flag BPF_F_ADJ_ROOM_ENCAP_L2_ETH
Date: Fri, 05 Mar 2021 16:10:07 +0000 [thread overview]
Message-ID: <161496060765.19509.6156916149397117488.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210304064046.6232-1-hxseverything@gmail.com>
Hello:
This patch was applied to bpf/bpf-next.git (refs/heads/master):
On Thu, 4 Mar 2021 14:40:46 +0800 you wrote:
> From: Xuesen Huang <huangxuesen@kuaishou.com>
>
> bpf_skb_adjust_room sets the inner_protocol as skb->protocol for packets
> encapsulation. But that is not appropriate when pushing Ethernet header.
>
> Add an option to further specify encap L2 type and set the inner_protocol
> as ETH_P_TEB.
>
> [...]
Here is the summary with links:
- [PATCH/v5] bpf: add bpf_skb_adjust_room flag BPF_F_ADJ_ROOM_ENCAP_L2_ETH
https://git.kernel.org/bpf/bpf-next/c/d01b59c9ae94
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:[~2021-03-05 16:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-04 6:40 [PATCH/v5] bpf: add bpf_skb_adjust_room flag BPF_F_ADJ_ROOM_ENCAP_L2_ETH Xuesen Huang
2021-03-04 13:55 ` Willem de Bruijn
2021-03-05 16:10 ` 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=161496060765.19509.6156916149397117488.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=chengzhiyong@kuaishou.com \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=huangxuesen@kuaishou.com \
--cc=hxseverything@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=wangli09@kuaishou.com \
--cc=willemb@google.com \
--cc=willemdebruijn.kernel@gmail.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