BPF List
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Larysa Zaremba <larysa.zaremba@intel.com>
Cc: bpf@vger.kernel.org, netdev@vger.kernel.org, ast@kernel.org,
	daniel@iogearbox.net, davem@davemloft.net, kuba@kernel.org,
	hawk@kernel.org, edumazet@google.com, magnus.karlsson@gmail.com,
	willemdebruijn.kernel@gmail.com, linyunsheng@huawei.com,
	maciej.fijalkowski@intel.com, john.fastabend@gmail.com,
	aleksander.lobakin@intel.com
Subject: Re: [PATCH bpf-next v4 0/2] Allow data_meta size > 32
Date: Mon, 11 Dec 2023 15:20:24 +0000	[thread overview]
Message-ID: <170230802414.23251.1943018178265573871.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231206205919.404415-1-larysa.zaremba@intel.com>

Hello:

This series was applied to bpf/bpf-next.git (master)
by Daniel Borkmann <daniel@iogearbox.net>:

On Wed,  6 Dec 2023 21:59:17 +0100 you wrote:
> Currently, there is no reason for data_meta to be limited to 32 bytes.
> Loosen this limitation and make maximum meta size 252 (max value of u8,
> aligned to 4). Details in the second patch.
> 
> Also, modify the selftest, so test_xdp_context_error does not complain
> about the unexpected success.
> 
> [...]

Here is the summary with links:
  - [bpf-next,v4,1/2] selftests/bpf: increase invalid metadata size
    https://git.kernel.org/bpf/bpf-next/c/15c79c6507c0
  - [bpf-next,v4,2/2] net, xdp: allow metadata > 32
    https://git.kernel.org/bpf/bpf-next/c/2ebe81c81435

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



      parent reply	other threads:[~2023-12-11 15:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-06 20:59 [PATCH bpf-next v4 0/2] Allow data_meta size > 32 Larysa Zaremba
2023-12-06 20:59 ` [PATCH bpf-next v4 1/2] selftests/bpf: increase invalid metadata size Larysa Zaremba
2023-12-06 20:59 ` [PATCH bpf-next v4 2/2] net, xdp: allow metadata > 32 Larysa Zaremba
2023-12-11 15:20 ` 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=170230802414.23251.1943018178265573871.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=aleksander.lobakin@intel.com \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=hawk@kernel.org \
    --cc=john.fastabend@gmail.com \
    --cc=kuba@kernel.org \
    --cc=larysa.zaremba@intel.com \
    --cc=linyunsheng@huawei.com \
    --cc=maciej.fijalkowski@intel.com \
    --cc=magnus.karlsson@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=willemdebruijn.kernel@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