From: kernel test robot <lkp@intel.com>
To: Masahiro Yamada <yamada.masahiro@socionext.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
Nathan Chancellor <natechancellor@gmail.com>
Subject: arch/m68k/include/asm/mcfmmu.h:102:20: sparse: void static inline mmu_write( ... )
Date: Fri, 5 Jun 2020 21:03:38 +0800 [thread overview]
Message-ID: <202006052133.71i4LnMM%lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2284 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 435faf5c218a47fd6258187f62d9bb1009717896
commit: 6863f5643dd717376c2fdc85a47a00f9d738a834 kbuild: allow Clang to find unused static inline functions for W=1 build
date: 9 months ago
config: m68k-randconfig-s031-20200605 (attached as .config)
compiler: m68k-linux-gcc (GCC) 9.3.0
reproduce:
# apt-get install sparse
# sparse version: v0.6.1-246-g41f651b4-dirty
git checkout 6863f5643dd717376c2fdc85a47a00f9d738a834
# save the attached .config to linux build tree
make W=1 C=1 ARCH=m68k CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__'
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
sparse warnings: (new ones prefixed by >>)
drivers/misc/habanalabs/debugfs.c:460:16: sparse: sparse: multiple definitions for function 'mmu_write'
arch/m68k/include/asm/mcfmmu.h:102:20: sparse: the previous one is here
drivers/misc/habanalabs/debugfs.c:460:16: sparse: sparse: symbol 'mmu_write' redeclared with different type (incompatible argument 1 (different base types)):
drivers/misc/habanalabs/debugfs.c:460:16: sparse: int static [signed] [toplevel] mmu_write( ... )
arch/m68k/include/asm/mcfmmu.h:102:20: sparse: note: previously declared as:
>> arch/m68k/include/asm/mcfmmu.h:102:20: sparse: void static inline [gnu_inline] [toplevel] mmu_write( ... )
vim +102 arch/m68k/include/asm/mcfmmu.h
8cee26f82a0c83 Greg Ungerer 2011-10-14 101
8cee26f82a0c83 Greg Ungerer 2011-10-14 @102 static inline void mmu_write(u32 a, u32 v)
8cee26f82a0c83 Greg Ungerer 2011-10-14 103 {
8cee26f82a0c83 Greg Ungerer 2011-10-14 104 *((volatile u32 *) a) = v;
8cee26f82a0c83 Greg Ungerer 2011-10-14 105 __asm__ __volatile__ ("nop");
8cee26f82a0c83 Greg Ungerer 2011-10-14 106 }
8cee26f82a0c83 Greg Ungerer 2011-10-14 107
:::::: The code at line 102 was first introduced by commit
:::::: 8cee26f82a0c830740db0267f828045cc39b90b9 m68k: definitions for the ColdFire V4e MMU hardware
:::::: TO: Greg Ungerer <gerg@uclinux.org>
:::::: CC: Greg Ungerer <gerg@uclinux.org>
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 29822 bytes --]
reply other threads:[~2020-06-05 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=202006052133.71i4LnMM%lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=natechancellor@gmail.com \
--cc=yamada.masahiro@socionext.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
all inboxes | Powered by JetHome®