From: Ross Zwisler <zwisler@google.com>
To: Ross Zwisler <zwisler@kernel.org>
Cc: linux-kernel@vger.kernel.org, Alexei Starovoitov <ast@kernel.org>,
Andrii Nakryiko <andrii@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Hao Luo <haoluo@google.com>, Jason Gunthorpe <jgg@ziepe.ca>,
Jiri Olsa <jolsa@kernel.org>,
John Fastabend <john.fastabend@gmail.com>,
KP Singh <kpsingh@kernel.org>, Leon Romanovsky <leon@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Martin KaFai Lau <martin.lau@linux.dev>,
Masami Hiramatsu <mhiramat@kernel.org>,
Mykola Lysenko <mykolal@fb.com>, Shuah Khan <shuah@kernel.org>,
Song Liu <song@kernel.org>, Stanislav Fomichev <sdf@google.com>,
Steven Rostedt <rostedt@goodmis.org>, Yonghong Song <yhs@fb.com>,
bpf@vger.kernel.org, linux-kselftest@vger.kernel.org,
linux-rdma@vger.kernel.org, linux-trace-kernel@vger.kernel.org
Subject: Re: [PATCH bpf-next v4 0/2] use canonical ftrace path whenever possible
Date: Mon, 13 Mar 2023 15:00:57 -0600 [thread overview]
Message-ID: <20230313210057.GB592900@google.com> (raw)
In-Reply-To: <20230313205628.1058720-1-zwisler@kernel.org>
On Mon, Mar 13, 2023 at 02:56:26PM -0600, Ross Zwisler wrote:
> From: Ross Zwisler <zwisler@google.com>
>
> v3 here:
> https://lore.kernel.org/all/20230310192050.4096886-1-zwisler@kernel.org/
Sorry, this should have been:
https://lore.kernel.org/all/20230310175209.2130880-1-zwisler@kernel.org/
>
> Changes since v3:
> * Added braces around a few multi-line if/else statements (Steven Rostedt)
> * Added Reviewed-by from Steven to patch 1
> * Rebased onto the current bpf/bpf-next
>
> Ross Zwisler (2):
> bpf: use canonical ftrace path
> selftests/bpf: use canonical ftrace path
>
> include/uapi/linux/bpf.h | 8 ++++----
> samples/bpf/cpustat_kern.c | 4 ++--
> samples/bpf/hbm.c | 4 ++--
> samples/bpf/ibumad_kern.c | 4 ++--
> samples/bpf/lwt_len_hist.sh | 2 +-
> samples/bpf/offwaketime_kern.c | 2 +-
> samples/bpf/task_fd_query_user.c | 4 ++--
> samples/bpf/test_lwt_bpf.sh | 2 +-
> samples/bpf/test_overhead_tp.bpf.c | 4 ++--
> tools/include/uapi/linux/bpf.h | 8 ++++----
> tools/testing/selftests/bpf/get_cgroup_id_user.c | 9 +++++++--
> .../selftests/bpf/prog_tests/kprobe_multi_test.c | 7 ++++++-
> .../selftests/bpf/prog_tests/task_fd_query_tp.c | 9 +++++++--
> .../selftests/bpf/prog_tests/tp_attach_query.c | 9 +++++++--
> .../testing/selftests/bpf/prog_tests/trace_printk.c | 10 +++++++---
> .../selftests/bpf/prog_tests/trace_vprintk.c | 10 +++++++---
> .../selftests/bpf/progs/test_stacktrace_map.c | 2 +-
> tools/testing/selftests/bpf/progs/test_tracepoint.c | 2 +-
> tools/testing/selftests/bpf/test_ftrace.sh | 7 ++++++-
> tools/testing/selftests/bpf/test_tunnel.sh | 13 +++++++++----
> tools/testing/selftests/bpf/trace_helpers.c | 8 ++++++--
> 21 files changed, 85 insertions(+), 43 deletions(-)
>
>
> base-commit: 22df776a9a866713d9decfb92b633bcfdb571954
> --
> 2.40.0.rc1.284.g88254d51c5-goog
>
prev parent reply other threads:[~2023-03-13 21:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-10 19:20 [PATCH v3 0/3] use canonical ftrace path whenever possible Ross Zwisler
2023-03-10 19:20 ` [PATCH v3 1/3] selftests: use canonical ftrace path Ross Zwisler
2023-03-10 19:20 ` [PATCH v3 2/3] leaking_addresses: also skip " Ross Zwisler
2023-03-10 19:20 ` [PATCH v3 3/3] tools/kvm_stat: use " Ross Zwisler
2023-03-13 20:56 ` [PATCH bpf-next v4 0/2] use canonical ftrace path whenever possible Ross Zwisler
2023-03-13 20:56 ` [PATCH bpf-next v4 1/2] bpf: use canonical ftrace path Ross Zwisler
2023-03-14 5:10 ` patchwork-bot+netdevbpf
2023-03-13 20:56 ` [PATCH bpf-next v4 2/2] selftests/bpf: " Ross Zwisler
2023-03-13 22:39 ` Steven Rostedt
2023-03-13 21:00 ` Ross Zwisler [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=20230313210057.GB592900@google.com \
--to=zwisler@google.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=haoluo@google.com \
--cc=jgg@ziepe.ca \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=martin.lau@linux.dev \
--cc=mhiramat@kernel.org \
--cc=mykolal@fb.com \
--cc=rostedt@goodmis.org \
--cc=sdf@google.com \
--cc=shuah@kernel.org \
--cc=song@kernel.org \
--cc=yhs@fb.com \
--cc=zwisler@kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.