From: Hou Tao <houtao1@huawei.com>
To: Lu Hongfei <luhongfei@vivo.com>
Cc: <opensource.kernel@vivo.com>, Andrii Nakryiko <andrii@kernel.org>,
Mykola Lysenko <mykolal@fb.com>,
Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Martin KaFai Lau <martin.lau@linux.dev>,
Song Liu <song@kernel.org>, Yonghong Song <yhs@fb.com>,
John Fastabend <john.fastabend@gmail.com>,
KP Singh <kpsingh@kernel.org>,
Stanislav Fomichev <sdf@google.com>, Hao Luo <haoluo@google.com>,
Jiri Olsa <jolsa@kernel.org>, Shuah Khan <shuah@kernel.org>,
Anton Protopopov <aspsk@isovalent.com>,
Wang Yufen <wangyufen@huawei.com>,
YiFei Zhu <zhuyifei@google.com>, <bpf@vger.kernel.org>,
<linux-kselftest@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 bpf-next] selftests/bpf: Corrected two typos
Date: Fri, 7 Jul 2023 17:17:34 +0800 [thread overview]
Message-ID: <b438d804-f73e-a5e4-0473-f21fa22a4486@huawei.com> (raw)
In-Reply-To: <20230707081253.34638-1-luhongfei@vivo.com>
On 7/7/2023 4:12 PM, Lu Hongfei wrote:
> When wrapping code, use ';' better than using ',' which is more
> in line with the coding habits of most engineers.
>
> Signed-off-by: Lu Hongfei <luhongfei@vivo.com>
> ---
> Compared to the previous version, the modifications made are:
> 1. Modified the subject to make it clearer and more accurate
> 2. Newly optimized typo in tcp_hdr_options.c
>
> tools/testing/selftests/bpf/benchs/bench_ringbufs.c | 2 +-
> tools/testing/selftests/bpf/prog_tests/tcp_hdr_options.c | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
Acked-by: Hou Tao <houtao1@huawei.com>
next prev parent reply other threads:[~2023-07-07 9:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-07 8:12 [PATCH v2 bpf-next] selftests/bpf: Corrected two typos Lu Hongfei
2023-07-07 9:17 ` Hou Tao [this message]
2023-07-07 16:54 ` Stanislav Fomichev
2023-07-07 17:40 ` patchwork-bot+netdevbpf
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=b438d804-f73e-a5e4-0473-f21fa22a4486@huawei.com \
--to=houtao1@huawei.com \
--cc=andrii@kernel.org \
--cc=aspsk@isovalent.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=luhongfei@vivo.com \
--cc=martin.lau@linux.dev \
--cc=mykolal@fb.com \
--cc=opensource.kernel@vivo.com \
--cc=sdf@google.com \
--cc=shuah@kernel.org \
--cc=song@kernel.org \
--cc=wangyufen@huawei.com \
--cc=yhs@fb.com \
--cc=zhuyifei@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 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.