From: kernel test robot <lkp@intel.com>
To: "Matthew Wilcox (Oracle)" <willy@infradead.org>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
x86@kernel.org
Subject: [tip:locking/core 23/38] drivers/char/nvram.c:56:21: warning: 'nvram_mutex' defined but not used
Date: Fri, 10 Apr 2026 21:05:53 +0800 [thread overview]
Message-ID: <202604102031.foCRIrmZ-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git locking/core
head: a21c1e961de28b95099a9ca2c3774b2eee1a33bb
commit: 25500ba7e77ce9d3d9b5a1929d41a2ee2e23f6fe [23/38] locking/mutex: Remove the list_head from struct mutex
config: powerpc64-randconfig-001-20260410 (https://download.01.org/0day-ci/archive/20260410/202604102031.foCRIrmZ-lkp@intel.com/config)
compiler: powerpc64-linux-gcc (GCC) 15.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260410/202604102031.foCRIrmZ-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/202604102031.foCRIrmZ-lkp@intel.com/
All warnings (new ones prefixed by >>):
In file included from include/linux/seqlock.h:20,
from include/linux/mmzone.h:17,
from include/linux/gfp.h:7,
from include/linux/umh.h:4,
from include/linux/kmod.h:9,
from include/linux/module.h:18,
from drivers/char/nvram.c:34:
>> drivers/char/nvram.c:56:21: warning: 'nvram_mutex' defined but not used [-Wunused-variable]
56 | static DEFINE_MUTEX(nvram_mutex);
| ^~~~~~~~~~~
include/linux/mutex.h:87:22: note: in definition of macro 'DEFINE_MUTEX'
87 | struct mutex mutexname = __MUTEX_INITIALIZER(mutexname)
| ^~~~~~~~~
vim +/nvram_mutex +56 drivers/char/nvram.c
^1da177e4c3f41 Linus Torvalds 2005-04-16 55
613655fa39ff69 Arnd Bergmann 2010-06-02 @56 static DEFINE_MUTEX(nvram_mutex);
^1da177e4c3f41 Linus Torvalds 2005-04-16 57 static DEFINE_SPINLOCK(nvram_state_lock);
^1da177e4c3f41 Linus Torvalds 2005-04-16 58 static int nvram_open_cnt; /* #times opened */
^1da177e4c3f41 Linus Torvalds 2005-04-16 59 static int nvram_open_mode; /* special open modes */
d5bbb5021ce8d9 Finn Thain 2019-01-15 60 static ssize_t nvram_size;
^1da177e4c3f41 Linus Torvalds 2005-04-16 61 #define NVRAM_WRITE 1 /* opened for writing (exclusive) */
^1da177e4c3f41 Linus Torvalds 2005-04-16 62 #define NVRAM_EXCL 2 /* opened with O_EXCL */
^1da177e4c3f41 Linus Torvalds 2005-04-16 63
:::::: The code at line 56 was first introduced by commit
:::::: 613655fa39ff6957754fa8ceb8559980920eb8ee drivers: autoconvert trivial BKL users to private mutex
:::::: TO: Arnd Bergmann <arnd@arndb.de>
:::::: CC: Arnd Bergmann <arnd@arndb.de>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-04-10 13:06 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=202604102031.foCRIrmZ-lkp@intel.com \
--to=lkp@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=willy@infradead.org \
--cc=x86@kernel.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