From: Stanislav Fomichev <sdf@google.com>
To: Hou Tao <houtao1@huawei.com>
Cc: Lu Hongfei <luhongfei@vivo.com>,
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>, 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 09:54:11 -0700 [thread overview]
Message-ID: <ZKhDMxVpu+w4Wb+t@google.com> (raw)
In-Reply-To: <b438d804-f73e-a5e4-0473-f21fa22a4486@huawei.com>
On 07/07, Hou Tao wrote:
>
>
> 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>
Acked-by: Stanislav Fomichev <sdf@google.com>
next prev parent reply other threads:[~2023-07-07 16:54 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
2023-07-07 16:54 ` Stanislav Fomichev [this message]
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=ZKhDMxVpu+w4Wb+t@google.com \
--to=sdf@google.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=houtao1@huawei.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=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox