Building the Linux kernel with Clang and LLVM
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: "Thomas Weißschuh " <linux@weissschuh.net>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: [thomas-weissschuh:b4/rust-kunit-assertion 11/13] lib/kunit/string-stream.c:111:47: warning: diagnostic behavior may be improved by adding the 'format(printf, 2, 3)' attribute to the declaration of 'kunit_string_stream_add'
Date: Mon, 05 Oct 2026 00:03:35 +0200	[thread overview]
Message-ID: <202610042350.99INxpQ7-lkp@intel.com> (raw)

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/thomas.weissschuh/linux.git b4/rust-kunit-assertion
head:   f72cd14d37a9483b1e310e75dc9e583adb82a6d2
commit: 99770826688f8794d7f46b2d703adf3270ed8744 [11/13] prep: string stream
config: x86_64-rhel-9.4-rust (https://download.01.org/0day-ci/archive/20261004/202610042350.99INxpQ7-lkp@intel.com/config)
compiler: clang version 22.1.8 (https://github.com/llvm/llvm-project ca7933e47d3a3451d81e72ac174dcb5aa28b59d1)
rustc: rustc 1.96.0 (ac68faa20 2026-05-25)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20261004/202610042350.99INxpQ7-lkp@intel.com/reproduce)

If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202610042350.99INxpQ7-lkp@intel.com/

All warnings (new ones prefixed by >>):

>> lib/kunit/string-stream.c:111:47: warning: diagnostic behavior may be improved by adding the 'format(printf, 2, 3)' attribute to the declaration of 'kunit_string_stream_add' [-Wmissing-format-attribute]
     111 |         result = string_stream_vadd(stream, fmt, args);
         |                                                      ^
   include/kunit/assert.h:232:5: note: 'kunit_string_stream_add' declared here
     232 | int kunit_string_stream_add(struct string_stream *stream, const char *fmt, ...);
         |     ^
   1 warning generated.


vim +111 lib/kunit/string-stream.c

   103	
   104	#if IS_ENABLED(CONFIG_RUST)
   105	int kunit_string_stream_add(struct string_stream *stream, const char *fmt, ...)
   106	{
   107		va_list args;
   108		int result;
   109	
   110		va_start(args, fmt);
 > 111		result = string_stream_vadd(stream, fmt, args);
   112		va_end(args);
   113	
   114		return result;
   115	}
   116	#endif
   117	

--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

                 reply	other threads:[~2026-10-04 22:04 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=202610042350.99INxpQ7-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=linux@weissschuh.net \
    --cc=llvm@lists.linux.dev \
    --cc=oe-kbuild-all@lists.linux.dev \
    /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