From: Kees Cook <kees@kernel.org>
To: Amer Al Shanawany <amer.shanawany@gmail.com>
Cc: 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,
Javier Carrasco <javier.carrasco.cruz@gmail.com>,
kernel test robot <lkp@intel.com>,
Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [PATCH v3] selftests: seccomp: fix format-zero-length warnings
Date: Wed, 12 Jun 2024 11:44:30 -0700 [thread overview]
Message-ID: <202406121144.0EE6C17FF@keescook> (raw)
In-Reply-To: <20240611151638.5767-1-amer.shanawany@gmail.com>
On Tue, Jun 11, 2024 at 05:16:08PM +0200, Amer Al Shanawany wrote:
> fix the following errors by using string format specifier and an empty
> parameter:
>
> 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/
> Suggested-by: Kees Cook <kees@kernel.org>
> Signed-off-by: Amer Al Shanawany <amer.shanawany@gmail.com>
Thanks!
Reviewed-by: Kees Cook <kees@kernel.org>
--
Kees Cook
prev parent reply other threads:[~2024-06-12 18:44 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 ` [PATCH v2] " Amer Al Shanawany
2024-06-07 20:58 ` 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 [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=202406121144.0EE6C17FF@keescook \
--to=kees@kernel.org \
--cc=amer.shanawany@gmail.com \
--cc=javier.carrasco.cruz@gmail.com \
--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