From: Andrew Morton <akpm@linux-foundation.org>
To: kernel test robot <lkp@intel.com>
Cc: Mike Rapoport <rppt@linux.ibm.com>,
kbuild-all@lists.01.org, Johannes Weiner <hannes@cmpxchg.org>,
Linux Memory Management List <linux-mm@kvack.org>
Subject: Re: [hnaz-linux-mm:master 60/194] include/linux/pgtable.h:74:27: error: redefinition of 'pte_offset_kernel'
Date: Tue, 9 Jun 2020 15:26:06 -0700 [thread overview]
Message-ID: <20200609152606.b08651fe680ee9c6e94540ad@linux-foundation.org> (raw)
In-Reply-To: <202006100010.WRBnCFU1%lkp@intel.com>
On Wed, 10 Jun 2020 00:12:12 +0800 kernel test robot <lkp@intel.com> wrote:
> tree: https://github.com/hnaz/linux-mm master
> head: a017b085735719105714da692a82a6eeb8830718
> commit: f48b9eb10f8c3f378ea4552fee58db3dea980e62 [60/194] mm: consolidate pte_index() and pte_offset_*() definitions
> config: sparc-defconfig (attached as .config)
> compiler: sparc-linux-gcc (GCC) 9.3.0
> reproduce (this is a W=1 build):
> wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
> chmod +x ~/bin/make.cross
> git checkout f48b9eb10f8c3f378ea4552fee58db3dea980e62
> # save the attached .config to linux build tree
> COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=sparc
>
> If you fix the issue, kindly add following tag as appropriate
> Reported-by: kernel test robot <lkp@intel.com>
>
> All error/warnings (new ones prefixed by >>, old ones prefixed by <<):
>
> In file included from include/linux/mm.h:31,
> from include/linux/memblock.h:13,
> from arch/sparc/mm/srmmu.c:14:
> >> include/linux/pgtable.h:74:27: error: redefinition of 'pte_offset_kernel'
> 74 | #define pte_offset_kernel pte_offset_kernel
> | ^~~~~~~~~~~~~~~~~
> >> arch/sparc/mm/srmmu.c:144:8: note: in expansion of macro 'pte_offset_kernel'
> 144 | pte_t *pte_offset_kernel(pmd_t *dir, unsigned long address)
> | ^~~~~~~~~~~~~~~~~
> include/linux/pgtable.h:70:22: note: previous definition of 'pte_offset_kernel' was here
> 70 | static inline pte_t *pte_offset_kernel(pmd_t *pmd, unsigned long address)
> | ^~~~~~~~~~~~~~~~~
> arch/sparc/mm/srmmu.c: In function 'poke_hypersparc':
> arch/sparc/mm/srmmu.c:1093:25: error: variable 'clear' set but not used [-Werror=unused-but-set-variable]
> 1093 | volatile unsigned long clear;
Well dang. The function was supposed to have been removed but
obviously this was lost during all the merging messes.
Mike, can you please confirm that this is still good?
--- a/arch/sparc/mm/srmmu.c~a
+++ a/arch/sparc/mm/srmmu.c
@@ -140,16 +140,6 @@ void pmd_set(pmd_t *pmdp, pte_t *ptep)
set_pte((pte_t *)&pmd_val(*pmdp), __pte(SRMMU_ET_PTD | ptp));
}
-/* Find an entry in the third-level page table.. */
-pte_t *pte_offset_kernel(pmd_t *dir, unsigned long address)
-{
- void *pte;
-
- pte = __nocache_va((pmd_val(*dir) & SRMMU_PTD_PMASK) << 4);
- return (pte_t *) pte +
- ((address >> PAGE_SHIFT) & (PTRS_PER_PTE - 1));
-}
-
/*
* size: bytes to allocate in the nocache area.
* align: bytes, number to align at.
_
next prev parent reply other threads:[~2020-06-09 22:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-09 16:12 kernel test robot
2020-06-09 22:26 ` Andrew Morton [this message]
2020-06-10 4:27 ` Mike Rapoport
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=20200609152606.b08651fe680ee9c6e94540ad@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=rppt@linux.ibm.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