From: Amer Al Shanawany <amer.shanawany@gmail.com>
To: Kees Cook <kees@kernel.org>,
Andy Lutomirski <luto@amacapital.net>,
Will Drewry <wad@chromium.org>, Shuah Khan <shuah@kernel.org>,
linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Javier Carrasco <javier.carrasco.cruz@gmail.com>,
kernel test robot <lkp@intel.com>,
Shuah Khan <skhan@linuxfoundation.org>,
Amer Al Shanawany <amer.shanawany@gmail.com>
Subject: [PATCH v2] selftests: seccomp: fix format-zero-length warnings
Date: Fri, 7 Jun 2024 14:41:18 +0200 [thread overview]
Message-ID: <20240607124117.66769-2-amer.shanawany@gmail.com> (raw)
In-Reply-To: <be032a65-e61b-40e0-a982-cb622ccca548@linuxfoundation.org>
fix the following errors by removing empty print statements:
seccomp_benchmark.c:197:24: warning: zero-length gnu_printf format
string [-Wformat-zero-length]
197 | ksft_print_msg("");
| ^~
seccomp_benchmark.c:202:24: warning: zero-length gnu_printf format
string [-Wformat-zero-length]
202 | ksft_print_msg("");
| ^~
seccomp_benchmark.c:204:24: warning: zero-length gnu_printf format
string [-Wformat-zero-length]
204 | ksft_print_msg("");
| ^~
Reported-by: kernel test robot <lkp@intel.com>
Closes: https://lore.kernel.org/oe-kbuild-all/202312260235.Uj5ug8K9-lkp@intel.com/
Signed-off-by: Amer Al Shanawany <amer.shanawany@gmail.com>
---
Changes v1 -> v2:
removed empty print statements
---
tools/testing/selftests/seccomp/seccomp_benchmark.c | 3 ---
1 file changed, 3 deletions(-)
diff --git a/tools/testing/selftests/seccomp/seccomp_benchmark.c b/tools/testing/selftests/seccomp/seccomp_benchmark.c
index b83099160fbc..6fe34be6c693 100644
--- a/tools/testing/selftests/seccomp/seccomp_benchmark.c
+++ b/tools/testing/selftests/seccomp/seccomp_benchmark.c
@@ -194,14 +194,11 @@ int main(int argc, char *argv[])
ksft_set_plan(7);
ksft_print_msg("Running on:\n");
- ksft_print_msg("");
system("uname -a");
ksft_print_msg("Current BPF sysctl settings:\n");
/* Avoid using "sysctl" which may not be installed. */
- ksft_print_msg("");
system("grep -H . /proc/sys/net/core/bpf_jit_enable");
- ksft_print_msg("");
system("grep -H . /proc/sys/net/core/bpf_jit_harden");
affinity();
--
2.43.0
next prev parent reply other threads:[~2024-06-07 12:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-03 11:54 [PATCH] selftests: seccomp: fix format-zero-length warnings Amer Al Shanawany
2024-06-06 22:41 ` Shuah Khan
2024-06-07 12:41 ` Amer Al Shanawany [this message]
2024-06-07 20:58 ` [PATCH v2] " Shuah Khan
2024-06-10 16:59 ` Kees Cook
2024-06-11 14:46 ` Shuah Khan
2024-06-11 15:16 ` [PATCH v3] " Amer Al Shanawany
2024-06-12 18:44 ` Kees Cook
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=20240607124117.66769-2-amer.shanawany@gmail.com \
--to=amer.shanawany@gmail.com \
--cc=javier.carrasco.cruz@gmail.com \
--cc=kees@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=lkp@intel.com \
--cc=luto@amacapital.net \
--cc=shuah@kernel.org \
--cc=skhan@linuxfoundation.org \
--cc=wad@chromium.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