BPF List
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Kaixi Fan <fankaixi.li@bytedance.com>
Cc: kafai@fb.com, songliubraving@fb.com, yhs@fb.com,
	john.fastabend@gmail.com, kpsingh@kernel.org,
	bpf@vger.kernel.org, ast@kernel.org, andrii@kernel.org,
	daniel@iogearbox.net
Subject: Re: [External] [PATCH bpf-next v6 0/3] Add source ip in bpf tunnel key
Date: Tue, 10 May 2022 18:00:13 +0000	[thread overview]
Message-ID: <165220561332.6035.6652465314332894275.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220430074844.69214-1-fankaixi.li@bytedance.com>

Hello:

This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:

On Sat, 30 Apr 2022 15:48:41 +0800 you wrote:
> From: Kaixi Fan <fankaixi.li@bytedance.com>
> 
> Now bpf code could not set tunnel source ip address of ip tunnel. So it
> could not support flow based tunnel mode completely. Because flow based
> tunnel mode could set tunnel source, destination ip address and tunnel
> key simultaneously.
> 
> [...]

Here is the summary with links:
  - [External,bpf-next,v6,1/3] bpf: Add source ip in "struct bpf_tunnel_key"
    https://git.kernel.org/bpf/bpf-next/c/26101f5ab6bd
  - [External,bpf-next,v6,2/3] selftests/bpf: Move vxlan tunnel testcases to test_progs
    https://git.kernel.org/bpf/bpf-next/c/1ee7efd40abf
  - [External,bpf-next,v6,3/3] selftests/bpf: Replace bpf_trace_printk in tunnel kernel code
    https://git.kernel.org/bpf/bpf-next/c/71b2ec21c331

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2022-05-10 18:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-30  7:48 [External] [PATCH bpf-next v6 0/3] Add source ip in bpf tunnel key fankaixi.li
2022-04-30  7:48 ` [External] [PATCH bpf-next v6 1/3] bpf: Add source ip in "struct bpf_tunnel_key" fankaixi.li
2022-04-30  7:48 ` [External] [PATCH bpf-next v6 2/3] selftests/bpf: Move vxlan tunnel testcases to test_progs fankaixi.li
2022-04-30  7:48 ` [External] [PATCH bpf-next v6 3/3] selftests/bpf: Replace bpf_trace_printk in tunnel kernel code fankaixi.li
2022-05-10 18:00 ` 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=165220561332.6035.6652465314332894275.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=fankaixi.li@bytedance.com \
    --cc=john.fastabend@gmail.com \
    --cc=kafai@fb.com \
    --cc=kpsingh@kernel.org \
    --cc=songliubraving@fb.com \
    --cc=yhs@fb.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