BPF List
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Stanislav Fomichev <sdf@google.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
	andrii@kernel.org, martin.lau@linux.dev, song@kernel.org,
	yhs@fb.com, john.fastabend@gmail.com, kpsingh@kernel.org,
	haoluo@google.com, jolsa@kernel.org
Subject: Re: [PATCH bpf-next 1/2] bpf: Resolve modifiers when walking structs
Date: Fri, 30 Jun 2023 08:40:20 +0000	[thread overview]
Message-ID: <168811442087.9995.12715014131569832899.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230626212522.2414485-1-sdf@google.com>

Hello:

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

On Mon, 26 Jun 2023 14:25:21 -0700 you wrote:
> It is impossible to use skb_frag_t in the tracing program.
> Resolve typedefs when walking structs.
> 
> Signed-off-by: Stanislav Fomichev <sdf@google.com>
> ---
>  kernel/bpf/btf.c | 2 ++
>  1 file changed, 2 insertions(+)

Here is the summary with links:
  - [bpf-next,1/2] bpf: Resolve modifiers when walking structs
    https://git.kernel.org/bpf/bpf-next/c/819d43428a86
  - [bpf-next,2/2] selftests/bpf: Add test to exercise typedef walking
    https://git.kernel.org/bpf/bpf-next/c/2597a25cb865

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-06-30  8:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-26 21:25 [PATCH bpf-next 1/2] bpf: Resolve modifiers when walking structs Stanislav Fomichev
2023-06-26 21:25 ` [PATCH bpf-next 2/2] selftests/bpf: Add test to exercise typedef walking Stanislav Fomichev
2023-06-27  5:06   ` Yonghong Song
2023-06-27  5:02 ` [PATCH bpf-next 1/2] bpf: Resolve modifiers when walking structs Yonghong Song
2023-06-30  8: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=168811442087.9995.12715014131569832899.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=haoluo@google.com \
    --cc=john.fastabend@gmail.com \
    --cc=jolsa@kernel.org \
    --cc=kpsingh@kernel.org \
    --cc=martin.lau@linux.dev \
    --cc=sdf@google.com \
    --cc=song@kernel.org \
    --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