From: kernel test robot <lkp@intel.com>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>,
Christophe Leroy <christophe.leroy@csgroup.eu>
Subject: arch/powerpc/mm/nohash/tlb_64e.c:36:5: sparse: sparse: symbol 'mmu_pte_psize' was not declared. Should it be static?
Date: Thu, 1 Aug 2024 13:06:46 +0800 [thread overview]
Message-ID: <202408011256.1O99IB0s-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 21b136cc63d2a9ddd60d4699552b69c214b32964
commit: a898530eea3d0ba08c17a60865995a3bb468d1bc powerpc/64e: split out nohash Book3E 64-bit code
date: 3 weeks ago
config: powerpc64-randconfig-r122-20240801 (https://download.01.org/0day-ci/archive/20240801/202408011256.1O99IB0s-lkp@intel.com/config)
compiler: powerpc64-linux-gcc (GCC) 14.1.0
reproduce: (https://download.01.org/0day-ci/archive/20240801/202408011256.1O99IB0s-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/202408011256.1O99IB0s-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> arch/powerpc/mm/nohash/tlb_64e.c:36:5: sparse: sparse: symbol 'mmu_pte_psize' was not declared. Should it be static?
arch/powerpc/mm/nohash/tlb_64e.c: note: in included file (through include/linux/mmzone.h, include/linux/gfp.h, include/linux/mm.h):
include/linux/page-flags.h:235:46: sparse: sparse: self-comparison always evaluates to false
include/linux/page-flags.h:235:46: sparse: sparse: self-comparison always evaluates to false
vim +/mmu_pte_psize +36 arch/powerpc/mm/nohash/tlb_64e.c
31
32 /* The variables below are currently only used on 64-bit Book3E
33 * though this will probably be made common with other nohash
34 * implementations at some point
35 */
> 36 int mmu_pte_psize; /* Page size used for PTE pages */
37 int mmu_vmemmap_psize; /* Page size used for the virtual mem map */
38 int book3e_htw_mode; /* HW tablewalk? Value is PPC_HTW_* */
39 unsigned long linear_map_top; /* Top of linear mapping */
40
41
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-08-01 5:07 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=202408011256.1O99IB0s-lkp@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=christophe.leroy@csgroup.eu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mpe@ellerman.id.au \
--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