public inbox for bpf@vger.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Daniel T. Lee <danieltimlee@gmail.com>
Cc: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
	martin.lau@linux.dev, song@kernel.org, yonghong.song@linux.dev,
	john.fastabend@gmail.com, kpsingh@kernel.org, sdf@google.com,
	haoluo@google.com, jolsa@kernel.org, axboe@kernel.dk,
	johannes.thumshirn@wdc.com, netdev@vger.kernel.org,
	bpf@vger.kernel.org
Subject: Re: [bpf-next 0/9] samples/bpf: make BPF programs more libbpf aware
Date: Mon, 21 Aug 2023 22:50:26 +0000	[thread overview]
Message-ID: <169265822645.19025.15250374334018816513.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230818090119.477441-1-danieltimlee@gmail.com>

Hello:

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

On Fri, 18 Aug 2023 18:01:10 +0900 you wrote:
> The existing tracing programs have been developed for a considerable
> period of time and, as a result, do not properly incorporate the
> features of the current libbpf, such as CO-RE. This is evident in
> frequent usage of functions like PT_REGS* and the persistence of "hack"
> methods using underscore-style bpf_probe_read_kernel from the past.
> These programs are far behind the current level of libbpf and can
> potentially confuse users.
> 
> [...]

Here is the summary with links:
  - [bpf-next,1/9] samples/bpf: fix warning with ignored-attributes
    https://git.kernel.org/bpf/bpf-next/c/34f6e38f58db
  - [bpf-next,2/9] samples/bpf: convert to vmlinux.h with tracing programs
    https://git.kernel.org/bpf/bpf-next/c/e7e6c774f5d4
  - [bpf-next,3/9] samples/bpf: unify bpf program suffix to .bpf with tracing programs
    https://git.kernel.org/bpf/bpf-next/c/4a0ee7889069
  - [bpf-next,4/9] samples/bpf: fix symbol mismatch by compiler optimization
    https://git.kernel.org/bpf/bpf-next/c/02dabc247ad6
  - [bpf-next,5/9] samples/bpf: make tracing programs to be more CO-RE centric
    https://git.kernel.org/bpf/bpf-next/c/11430421b440
  - [bpf-next,6/9] samples/bpf: fix bio latency check with tracepoint
    https://git.kernel.org/bpf/bpf-next/c/92632115fb57
  - [bpf-next,7/9] samples/bpf: fix broken map lookup probe
    https://git.kernel.org/bpf/bpf-next/c/d93a7cf6ca2c
  - [bpf-next,8/9] samples/bpf: refactor syscall tracing programs using BPF_KSYSCALL macro
    https://git.kernel.org/bpf/bpf-next/c/8dc805514631
  - [bpf-next,9/9] samples/bpf: simplify spintest with kprobe.multi
    https://git.kernel.org/bpf/bpf-next/c/456d53554ca7

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-08-21 22:50 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-18  9:01 [bpf-next 0/9] samples/bpf: make BPF programs more libbpf aware Daniel T. Lee
2023-08-18  9:01 ` [bpf-next 1/9] samples/bpf: fix warning with ignored-attributes Daniel T. Lee
2023-08-18  9:01 ` [bpf-next 2/9] samples/bpf: convert to vmlinux.h with tracing programs Daniel T. Lee
2023-08-18  9:01 ` [bpf-next 3/9] samples/bpf: unify bpf program suffix to .bpf " Daniel T. Lee
2023-08-18  9:01 ` [bpf-next 4/9] samples/bpf: fix symbol mismatch by compiler optimization Daniel T. Lee
2023-08-18  9:01 ` [bpf-next 5/9] samples/bpf: make tracing programs to be more CO-RE centric Daniel T. Lee
2023-08-18  9:01 ` [bpf-next 6/9] samples/bpf: fix bio latency check with tracepoint Daniel T. Lee
2023-08-18  9:01 ` [bpf-next 7/9] samples/bpf: fix broken map lookup probe Daniel T. Lee
2023-08-18  9:01 ` [bpf-next 8/9] samples/bpf: refactor syscall tracing programs using BPF_KSYSCALL macro Daniel T. Lee
2023-08-18  9:01 ` [bpf-next 9/9] samples/bpf: simplify spintest with kprobe.multi Daniel T. Lee
2023-08-21 22: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=169265822645.19025.15250374334018816513.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=axboe@kernel.dk \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=danieltimlee@gmail.com \
    --cc=haoluo@google.com \
    --cc=johannes.thumshirn@wdc.com \
    --cc=john.fastabend@gmail.com \
    --cc=jolsa@kernel.org \
    --cc=kpsingh@kernel.org \
    --cc=martin.lau@linux.dev \
    --cc=netdev@vger.kernel.org \
    --cc=sdf@google.com \
    --cc=song@kernel.org \
    --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