public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Marcus Wichelmann <marcus.wichelmann@hetzner-cloud.de>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	bpf@vger.kernel.org, linux-kselftest@vger.kernel.org,
	willemdebruijn.kernel@gmail.com, jasowang@redhat.com,
	andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
	kuba@kernel.org, pabeni@redhat.com, andrii@kernel.org,
	eddyz87@gmail.com, mykolal@fb.com, ast@kernel.org,
	daniel@iogearbox.net, martin.lau@linux.dev, song@kernel.org,
	yonghong.song@linux.dev, john.fastabend@gmail.com,
	kpsingh@kernel.org, sdf@fomichev.me, haoluo@google.com,
	jolsa@kernel.org, shuah@kernel.org, hawk@kernel.org
Subject: Re: [PATCH bpf-next v5 0/6] XDP metadata support for tun driver
Date: Thu, 06 Mar 2025 20:40:34 +0000	[thread overview]
Message-ID: <174129363479.1769540.9069391610888799796.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250305213438.3863922-1-marcus.wichelmann@hetzner-cloud.de>

Hello:

This series was applied to bpf/bpf-next.git (net)
by Martin KaFai Lau <martin.lau@kernel.org>:

On Wed,  5 Mar 2025 21:34:32 +0000 you wrote:
> Hi all,
> 
> this v5 of the patch series is very similar to v4, but rebased onto the
> bpf-next/net branch instead of bpf-next/master.
> Because the commit c047e0e0e435 ("selftests/bpf: Optionally open a
> dedicated namespace to run test in it") is not yet included in this branch,
> I changed the xdp_context_tuntap test to manually create a namespace to run
> the test in.
> 
> [...]

Here is the summary with links:
  - [bpf-next,v5,1/6] net: tun: enable XDP metadata support
    https://git.kernel.org/bpf/bpf-next/c/c2315ebb0588
  - [bpf-next,v5,2/6] net: tun: enable transfer of XDP metadata to skb
    https://git.kernel.org/bpf/bpf-next/c/0ca23a4d64ce
  - [bpf-next,v5,3/6] selftests/bpf: move open_tuntap to network helpers
    https://git.kernel.org/bpf/bpf-next/c/d5ca409c86d3
  - [bpf-next,v5,4/6] selftests/bpf: refactor xdp_context_functional test and bpf program
    https://git.kernel.org/bpf/bpf-next/c/b46aa22b66d3
  - [bpf-next,v5,5/6] selftests/bpf: add test for XDP metadata support in tun driver
    https://git.kernel.org/bpf/bpf-next/c/73eeecc3cdfe
  - [bpf-next,v5,6/6] selftests/bpf: fix file descriptor assertion in open_tuntap helper
    https://git.kernel.org/bpf/bpf-next/c/49306d5bfc6a

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



      parent reply	other threads:[~2025-03-06 20:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-05 21:34 [PATCH bpf-next v5 0/6] XDP metadata support for tun driver Marcus Wichelmann
2025-03-05 21:34 ` [PATCH bpf-next v5 1/6] net: tun: enable XDP metadata support Marcus Wichelmann
2025-03-05 21:34 ` [PATCH bpf-next v5 2/6] net: tun: enable transfer of XDP metadata to skb Marcus Wichelmann
2025-03-05 21:34 ` [PATCH bpf-next v5 3/6] selftests/bpf: move open_tuntap to network helpers Marcus Wichelmann
2025-03-05 21:34 ` [PATCH bpf-next v5 4/6] selftests/bpf: refactor xdp_context_functional test and bpf program Marcus Wichelmann
2025-03-05 21:34 ` [PATCH bpf-next v5 5/6] selftests/bpf: add test for XDP metadata support in tun driver Marcus Wichelmann
2025-03-05 21:34 ` [PATCH bpf-next v5 6/6] selftests/bpf: fix file descriptor assertion in open_tuntap helper Marcus Wichelmann
2025-03-06 20: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=174129363479.1769540.9069391610888799796.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrew+netdev@lunn.ch \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=davem@davemloft.net \
    --cc=eddyz87@gmail.com \
    --cc=edumazet@google.com \
    --cc=haoluo@google.com \
    --cc=hawk@kernel.org \
    --cc=jasowang@redhat.com \
    --cc=john.fastabend@gmail.com \
    --cc=jolsa@kernel.org \
    --cc=kpsingh@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=marcus.wichelmann@hetzner-cloud.de \
    --cc=martin.lau@linux.dev \
    --cc=mykolal@fb.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=sdf@fomichev.me \
    --cc=shuah@kernel.org \
    --cc=song@kernel.org \
    --cc=willemdebruijn.kernel@gmail.com \
    --cc=yonghong.song@linux.dev \
    /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