Building the Linux kernel with Clang and LLVM
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: "Stefan Dösinger " <stefandoesinger@gmail.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: [stefandoesinger-zx297520:dlink 70/131] drivers/rpmsg/zx29_smd.c:51:13: warning: variable 'huh' set but not used
Date: Thu, 03 Sep 2026 06:51:55 +0800	[thread overview]
Message-ID: <202609030640.2vjAUQKU-lkp@intel.com> (raw)

tree:   https://gitlab.com/stefandoesinger/zx297520-kernel dlink
head:   4132307830800b020a6d29d27cb3fec3cb5fbb90
commit: f845ca09dab5001db7890c5242662a1ad134fcf3 [70/131] Even more working rpmsg
config: hexagon-allmodconfig (https://download.01.org/0day-ci/archive/20260903/202609030640.2vjAUQKU-lkp@intel.com/config)
compiler: clang version 24.0.0git (https://github.com/llvm/llvm-project 2c2cffa015e9549aafba9e514384b08204c7cc4b)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260903/202609030640.2vjAUQKU-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/202609030640.2vjAUQKU-lkp@intel.com/

All warnings (new ones prefixed by >>):

   drivers/rpmsg/zx29_smd.c:189:13: warning: unused function 'zx29_smd_release_device' [-Wunused-function]
     189 | static void zx29_smd_release_device(struct device *dev)
         |             ^~~~~~~~~~~~~~~~~~~~~~~
>> drivers/rpmsg/zx29_smd.c:51:13: warning: variable 'huh' set but not used [-Wunused-but-set-global]
      51 | static u32 *huh;
         |             ^
   2 warnings generated.


vim +/huh +51 drivers/rpmsg/zx29_smd.c

    50	
  > 51	static u32 *huh;
    52	

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

                 reply	other threads:[~2026-09-02 22:52 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=202609030640.2vjAUQKU-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=llvm@lists.linux.dev \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=stefandoesinger@gmail.com \
    /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