From: Xu Kuohai <xukuohai@huawei.com>
To: Song Liu <songliubraving@fb.com>
Cc: bpf <bpf@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
open list <linux-kernel@vger.kernel.org>,
Networking <netdev@vger.kernel.org>,
"open list:KERNEL SELFTEST FRAMEWORK"
<linux-kselftest@vger.kernel.org>, Will Deacon <will@kernel.org>,
Steven Rostedt <rostedt@goodmis.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Alexei Starovoitov <ast@kernel.org>,
Zi Shen Lim <zlim.lnx@gmail.com>,
Andrii Nakryiko <andrii@kernel.org>, Martin Lau <kafai@fb.com>,
Yonghong Song <yhs@fb.com>,
John Fastabend <john.fastabend@gmail.com>,
KP Singh <kpsingh@kernel.org>, X86 ML <x86@kernel.org>,
"H. Peter Anvin" <hpa@zytor.com>, Shuah Khan <shuah@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Ard Biesheuvel <ardb@kernel.org>,
Pasha Tatashin <pasha.tatashin@soleen.com>,
Peter Collingbourne <pcc@google.com>,
Daniel Kiss <daniel.kiss@arm.com>,
Sudeep Holla <sudeep.holla@arm.com>,
Steven Price <steven.price@arm.com>,
Marc Zyngier <maz@kernel.org>, Mark Brown <broonie@kernel.org>,
Kumar Kartikeya Dwivedi <memxor@gmail.com>,
Delyan Kratunov <delyank@fb.com>
Subject: Re: [PATCH bpf-next 1/5] arm64: ftrace: Add ftrace direct call support
Date: Thu, 14 Apr 2022 14:35:26 +0800 [thread overview]
Message-ID: <d405cd60-c071-0daf-3174-670d1c8a2009@huawei.com> (raw)
In-Reply-To: <D829ABEB-5504-4682-9A20-AAD21AFE3CB3@fb.com>
On 4/14/2022 1:58 PM, Song Liu wrote:
> Just one nitpick for 2/5: as we move is_valid_bpf_tramp_flags to
> trampoline.c, we should change the multi-line comment into net
> style:
Thanks for your suggestion, will fix in v2.
next prev parent reply other threads:[~2022-04-14 6:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-13 5:49 [PATCH bpf-next 0/5] bpf trampoline for arm64 Xu Kuohai
2022-04-13 5:49 ` [PATCH bpf-next 1/5] arm64: ftrace: Add ftrace direct call support Xu Kuohai
2022-04-14 5:58 ` Song Liu
2022-04-14 6:35 ` Xu Kuohai [this message]
2022-04-13 5:49 ` [PATCH bpf-next 2/5] bpf: Move is_valid_bpf_tramp_flags() to the public trampoline code Xu Kuohai
2022-04-13 5:49 ` [PATCH bpf-next 3/5] bpf, arm64: Impelment bpf_arch_text_poke() for arm64 Xu Kuohai
2022-04-13 5:49 ` [PATCH bpf-next 4/5] bpf, arm64: bpf trampoline " Xu Kuohai
2022-04-13 5:49 ` [PATCH bpf-next 5/5] selftests/bpf: Fix trivial typo in fentry_fexit.c Xu Kuohai
2022-04-13 18:34 ` [PATCH bpf-next 0/5] bpf trampoline for arm64 Toke Høiland-Jørgensen
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=d405cd60-c071-0daf-3174-670d1c8a2009@huawei.com \
--to=xukuohai@huawei.com \
--cc=andrii@kernel.org \
--cc=ardb@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=broonie@kernel.org \
--cc=daniel.kiss@arm.com \
--cc=daniel@iogearbox.net \
--cc=delyank@fb.com \
--cc=hpa@zytor.com \
--cc=john.fastabend@gmail.com \
--cc=kafai@fb.com \
--cc=kpsingh@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=maz@kernel.org \
--cc=memxor@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pasha.tatashin@soleen.com \
--cc=pcc@google.com \
--cc=rostedt@goodmis.org \
--cc=shuah@kernel.org \
--cc=songliubraving@fb.com \
--cc=steven.price@arm.com \
--cc=sudeep.holla@arm.com \
--cc=will@kernel.org \
--cc=x86@kernel.org \
--cc=yhs@fb.com \
--cc=zlim.lnx@gmail.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