From: Stanislav Fomichev <sdf@google.com>
To: Rong Tao <rtoax@foxmail.com>
Cc: alexandre.torgue@foss.st.com, andrii@kernel.org, ast@kernel.org,
bpf@vger.kernel.org, chantr4@gmail.com, daniel@iogearbox.net,
deso@posteo.net, eddyz87@gmail.com, haoluo@google.com,
iii@linux.ibm.com, john.fastabend@gmail.com, jolsa@kernel.org,
kpsingh@kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com, martin.lau@linux.dev,
mcoquelin.stm32@gmail.com, mykolal@fb.com, rongtao@cestc.cn,
rostedt@goodmis.org, shuah@kernel.org, song@kernel.org,
xukuohai@huawei.com, yonghong.song@linux.dev, zwisler@google.com
Subject: Re: [PATCH bpf-next] selftests/bpf: trace_helpers.c: optimize kallsyms cache
Date: Fri, 11 Aug 2023 09:59:54 -0700 [thread overview]
Message-ID: <ZNZpCqw7YiN7H3mU@google.com> (raw)
In-Reply-To: <tencent_9C20DA1AB80A0564315EF2A91CBF7A8C260A@qq.com>
On 08/11, Rong Tao wrote:
> Thanks for your advise, you are right, i just submit v2 [0].
>
> I just found that, because of the modified patch, your email address was not
> obtained through scripts/get_maintainer.pl, so the v2 [0] email was not sent
> to you, sorry.
No worries, as long as it reaches the list I'll get to it :-)
prev parent reply other threads:[~2023-08-11 17:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-10 15:14 [PATCH bpf-next] selftests/bpf: trace_helpers.c: optimize kallsyms cache Rong Tao
2023-08-10 18:09 ` Stanislav Fomichev
2023-08-11 0:01 ` Rong Tao
2023-08-11 16:59 ` Stanislav Fomichev [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=ZNZpCqw7YiN7H3mU@google.com \
--to=sdf@google.com \
--cc=alexandre.torgue@foss.st.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=chantr4@gmail.com \
--cc=daniel@iogearbox.net \
--cc=deso@posteo.net \
--cc=eddyz87@gmail.com \
--cc=haoluo@google.com \
--cc=iii@linux.ibm.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=martin.lau@linux.dev \
--cc=mcoquelin.stm32@gmail.com \
--cc=mykolal@fb.com \
--cc=rongtao@cestc.cn \
--cc=rostedt@goodmis.org \
--cc=rtoax@foxmail.com \
--cc=shuah@kernel.org \
--cc=song@kernel.org \
--cc=xukuohai@huawei.com \
--cc=yonghong.song@linux.dev \
--cc=zwisler@google.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