From: shijie001@208suo.com
To: andrii@kernel.org, daniel@iogearbox.net, shuah@kernel.org
Cc: bpf@vger.kernel.org, linux-kselftest@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [PATCH] selftests/bpf: Fix errors in log_fixup.c
Date: Mon, 17 Jul 2023 15:56:47 +0800 [thread overview]
Message-ID: <2dc1d837343d3880057aee05dd047a57@208suo.com> (raw)
In-Reply-To: <tencent_E184AD3DB9CAB3F8C7DCDE620D5C2218F90A@qq.com>
The following checkpatch errors are removed:
ERROR: "foo* bar" should be "foo *bar"
Signed-off-by: Jie Shi <shijie001@208suo.com>
---
tools/testing/selftests/bpf/prog_tests/log_fixup.c | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/tools/testing/selftests/bpf/prog_tests/log_fixup.c
b/tools/testing/selftests/bpf/prog_tests/log_fixup.c
index dba71d98a227..69959748d466 100644
--- a/tools/testing/selftests/bpf/prog_tests/log_fixup.c
+++ b/tools/testing/selftests/bpf/prog_tests/log_fixup.c
@@ -14,7 +14,7 @@ enum trunc_type {
static void bad_core_relo(size_t log_buf_size, enum trunc_type
trunc_type)
{
char log_buf[8 * 1024];
- struct test_log_fixup* skel;
+ struct test_log_fixup *skel;
int err;
skel = test_log_fixup__open();
@@ -72,7 +72,7 @@ static void bad_core_relo(size_t log_buf_size, enum
trunc_type trunc_type)
static void bad_core_relo_subprog(void)
{
char log_buf[8 * 1024];
- struct test_log_fixup* skel;
+ struct test_log_fixup *skel;
int err;
skel = test_log_fixup__open();
@@ -104,7 +104,7 @@ static void bad_core_relo_subprog(void)
static void missing_map(void)
{
char log_buf[8 * 1024];
- struct test_log_fixup* skel;
+ struct test_log_fixup *skel;
int err;
skel = test_log_fixup__open();
@@ -138,7 +138,7 @@ static void missing_map(void)
static void missing_kfunc(void)
{
char log_buf[8 * 1024];
- struct test_log_fixup* skel;
+ struct test_log_fixup *skel;
int err;
skel = test_log_fixup__open();
parent reply other threads:[~2023-07-17 7:56 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <tencent_E184AD3DB9CAB3F8C7DCDE620D5C2218F90A@qq.com>]
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=2dc1d837343d3880057aee05dd047a57@208suo.com \
--to=shijie001@208suo.com \
--cc=andrii@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=shuah@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
all inboxes | Powered by JetHome®