From: patchwork-bot+netdevbpf@kernel.org
To: Ross Zwisler <zwisler@kernel.org>
Cc: linux-kernel@vger.kernel.org, zwisler@google.com, ast@kernel.org,
andrii@kernel.org, daniel@iogearbox.net, haoluo@google.com,
jgg@ziepe.ca, jolsa@kernel.org, john.fastabend@gmail.com,
kpsingh@kernel.org, leon@kernel.org, mark.rutland@arm.com,
martin.lau@linux.dev, mhiramat@kernel.org, mykolal@fb.com,
shuah@kernel.org, song@kernel.org, sdf@google.com,
rostedt@goodmis.org, yhs@fb.com, bpf@vger.kernel.org,
linux-kselftest@vger.kernel.org, linux-rdma@vger.kernel.org,
linux-trace-kernel@vger.kernel.org, mst@redhat.com
Subject: Re: [PATCH bpf-next v4 1/2] bpf: use canonical ftrace path
Date: Tue, 14 Mar 2023 05:10:17 +0000 [thread overview]
Message-ID: <167877061717.18868.4284758514562021959.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230313205628.1058720-2-zwisler@kernel.org>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Mon, 13 Mar 2023 14:56:27 -0600 you wrote:
> From: Ross Zwisler <zwisler@google.com>
>
> The canonical location for the tracefs filesystem is at /sys/kernel/tracing.
>
> But, from Documentation/trace/ftrace.rst:
>
> Before 4.1, all ftrace tracing control files were within the debugfs
> file system, which is typically located at /sys/kernel/debug/tracing.
> For backward compatibility, when mounting the debugfs file system,
> the tracefs file system will be automatically mounted at:
>
> [...]
Here is the summary with links:
- [bpf-next,v4,1/2] bpf: use canonical ftrace path
https://git.kernel.org/bpf/bpf-next/c/27d7fdf06fdb
- [bpf-next,v4,2/2] selftests/bpf: use canonical ftrace path
https://git.kernel.org/bpf/bpf-next/c/ab4c15feb2eb
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2023-03-14 5:10 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 [this message]
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 ` [PATCH bpf-next v4 0/2] use canonical ftrace path whenever possible Ross Zwisler
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=167877061717.18868.4284758514562021959.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=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=mst@redhat.com \
--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@google.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox