linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: oe-kbuild-all@lists.linux.dev,
	Linux Memory Management List <linux-mm@kvack.org>
Subject: [linux-next:master 3550/3551] arch/sparc/mm/srmmu.c:1082:32: warning: variable 'clear' set but not used
Date: Mon, 27 Nov 2023 18:20:43 +0800	[thread overview]
Message-ID: <202311271753.9HEOvyqm-lkp@intel.com> (raw)

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head:   48bbaf8b793e0770798519f8ee1ea2908ff0943a
commit: 233d97f67e6525aff8a621735926a8acbd980ca1 [3550/3551] sparc: turn off Werror for now
config: sparc-allnoconfig (https://download.01.org/0day-ci/archive/20231127/202311271753.9HEOvyqm-lkp@intel.com/config)
compiler: sparc-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231127/202311271753.9HEOvyqm-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/202311271753.9HEOvyqm-lkp@intel.com/

All warnings (new ones prefixed by >>):

   arch/sparc/mm/srmmu.c: In function 'poke_hypersparc':
>> arch/sparc/mm/srmmu.c:1082:32: warning: variable 'clear' set but not used [-Wunused-but-set-variable]
    1082 |         volatile unsigned long clear;
         |                                ^~~~~
--
   arch/sparc/mm/leon_mm.c: In function 'leon_swprobe':
>> arch/sparc/mm/leon_mm.c:42:32: warning: variable 'paddrbase' set but not used [-Wunused-but-set-variable]
      42 |         unsigned int lvl, pte, paddrbase;
         |                                ^~~~~~~~~


vim +/clear +1082 arch/sparc/mm/srmmu.c

^1da177e4c3f41 Linus Torvalds 2005-04-16  1079  
2066aadd53c563 Paul Gortmaker 2013-06-17  1080  static void poke_hypersparc(void)
^1da177e4c3f41 Linus Torvalds 2005-04-16  1081  {
^1da177e4c3f41 Linus Torvalds 2005-04-16 @1082  	volatile unsigned long clear;
^1da177e4c3f41 Linus Torvalds 2005-04-16  1083  	unsigned long mreg = srmmu_get_mmureg();
^1da177e4c3f41 Linus Torvalds 2005-04-16  1084  
^1da177e4c3f41 Linus Torvalds 2005-04-16  1085  	hyper_flush_unconditional_combined();
^1da177e4c3f41 Linus Torvalds 2005-04-16  1086  
^1da177e4c3f41 Linus Torvalds 2005-04-16  1087  	mreg &= ~(HYPERSPARC_CWENABLE);
^1da177e4c3f41 Linus Torvalds 2005-04-16  1088  	mreg |= (HYPERSPARC_CENABLE | HYPERSPARC_WBENABLE);
^1da177e4c3f41 Linus Torvalds 2005-04-16  1089  	mreg |= (HYPERSPARC_CMODE);
^1da177e4c3f41 Linus Torvalds 2005-04-16  1090  
^1da177e4c3f41 Linus Torvalds 2005-04-16  1091  	srmmu_set_mmureg(mreg);
^1da177e4c3f41 Linus Torvalds 2005-04-16  1092  

:::::: The code at line 1082 was first introduced by commit
:::::: 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 Linux-2.6.12-rc2

:::::: TO: Linus Torvalds <torvalds@ppc970.osdl.org>
:::::: CC: Linus Torvalds <torvalds@ppc970.osdl.org>

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


                 reply	other threads:[~2023-11-27 10:22 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=202311271753.9HEOvyqm-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=linux-mm@kvack.org \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=sfr@canb.auug.org.au \
    /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