BPF Archive mirror
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Martin KaFai Lau <martin.lau@linux.dev>
Cc: bpf@vger.kernel.org, ast@kernel.org, andrii@kernel.org,
	daniel@iogearbox.net, kernel-team@meta.com
Subject: Re: [PATCH bpf-next] selftests/bpf: Use bpf_tracing.h instead of bpf_tcp_helpers.h
Date: Mon, 06 May 2024 20:50:28 +0000	[thread overview]
Message-ID: <171502862894.17124.3307277720723637686.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240504005045.848376-1-martin.lau@linux.dev>

Hello:

This patch was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@kernel.org>:

On Fri,  3 May 2024 17:50:45 -0700 you wrote:
> From: Martin KaFai Lau <martin.lau@kernel.org>
> 
> The bpf programs that this patch changes require the BPF_PROG macro.
> The BPF_PROG macro is defined in the libbpf's bpf_tracing.h.
> Some tests include bpf_tcp_helpers.h which includes bpf_tracing.h.
> They don't need other things from bpf_tcp_helpers.h other than
> bpf_tracing.h. This patch simplifies it by directly including
> the bpf_tracing.h.
> 
> [...]

Here is the summary with links:
  - [bpf-next] selftests/bpf: Use bpf_tracing.h instead of bpf_tcp_helpers.h
    https://git.kernel.org/bpf/bpf-next/c/8e6d9ae2e09f

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



      reply	other threads:[~2024-05-06 20:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-04  0:50 [PATCH bpf-next] selftests/bpf: Use bpf_tracing.h instead of bpf_tcp_helpers.h Martin KaFai Lau
2024-05-06 20:50 ` 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=171502862894.17124.3307277720723637686.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=kernel-team@meta.com \
    --cc=martin.lau@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).