Building the Linux kernel with Clang and LLVM
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Dmitry Baryshkov <lumag@kernel.org>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: [lumag-msm:venus-8996-vmem 21/173] drivers/media/platform/qcom/venus/core.c:436:45: warning: diagnostic behavior may be improved by adding the 'format(printf, 2, 3)' attribute to the declaration of 'venus_fwtrace_add'
Date: Thu, 22 Oct 2026 06:10:34 +0800	[thread overview]
Message-ID: <202610220601.FUv6hw4D-lkp@intel.com> (raw)

tree:   https://gitlab.freedesktop.org/lumag/msm venus-8996-vmem
head:   4dff7b31dd13e97b8f7abab7bc115d2875afd5e8
commit: 1c74759d645846cbcdd7907ffae600567bfdb220 [21/173] DEBUG: media: venus: trace firmware messages and HFI commands
config: arm64-allmodconfig (https://download.01.org/0day-ci/archive/20261022/202610220601.FUv6hw4D-lkp@intel.com/config)
compiler: clang version 24.0.0git (https://github.com/llvm/llvm-project 2c419645e808a6667eee9dbb16c828f77e2fd2f0)
rustc: rustc 1.96.0 (ac68faa20 2026-05-25)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20261022/202610220601.FUv6hw4D-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/202610220601.FUv6hw4D-lkp@intel.com/

All warnings (new ones prefixed by >>):

>> drivers/media/platform/qcom/venus/core.c:436:45: warning: diagnostic behavior may be improved by adding the 'format(printf, 2, 3)' attribute to the declaration of 'venus_fwtrace_add' [-Wmissing-format-attribute]
     436 |         vsnprintf(e->msg, sizeof(e->msg), fmt, args);
         |                                                    ^
   drivers/media/platform/qcom/venus/core.h:50:6: note: 'venus_fwtrace_add' declared here
      50 | void venus_fwtrace_add(struct venus_core *core, const char *fmt, ...);
         |      ^
   1 warning generated.


vim +436 drivers/media/platform/qcom/venus/core.c

   423	
   424	void venus_fwtrace_add(struct venus_core *core, const char *fmt, ...)
   425	{
   426		struct venus_fwtrace_entry *e;
   427		unsigned long flags;
   428		va_list args;
   429	
   430		spin_lock_irqsave(&core->fwtrace_lock, flags);
   431	
   432		e = &core->fwtrace[core->fwtrace_head];
   433		e->ts = local_clock();
   434	
   435		va_start(args, fmt);
 > 436		vsnprintf(e->msg, sizeof(e->msg), fmt, args);
   437		va_end(args);
   438	
   439		core->fwtrace_head++;
   440		if (core->fwtrace_head == VENUS_FWTRACE_ENTRIES) {
   441			core->fwtrace_head = 0;
   442			core->fwtrace_wrapped = true;
   443		}
   444	
   445		spin_unlock_irqrestore(&core->fwtrace_lock, flags);
   446	}
   447	

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

                 reply	other threads:[~2026-10-21 22:11 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=202610220601.FUv6hw4D-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=llvm@lists.linux.dev \
    --cc=lumag@kernel.org \
    --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