public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org
Subject: arch/m68k/coldfire/m523x.c:31:19: sparse: sparse: symbol 'm523x_clk_lookup' was not declared. Should it be static?
Date: Sat, 13 Nov 2021 03:35:53 +0800	[thread overview]
Message-ID: <202111130330.fhEpFYvX-lkp@intel.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 2237 bytes --]

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head:   5833291ab6de9c3e2374336b51c814e515e8f3a5
commit: 63aadb77669a6856b26d73da85b4f788731524a3 m68k: coldfire: use clkdev_lookup on most coldfire
date:   5 months ago
config: m68k-randconfig-s032-20211027 (attached as .config)
compiler: m68k-linux-gcc (GCC) 11.2.0
reproduce:
        wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        # apt-get install sparse
        # sparse version: v0.6.4-dirty
        # https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=63aadb77669a6856b26d73da85b4f788731524a3
        git remote add linus https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
        git fetch --no-tags linus master
        git checkout 63aadb77669a6856b26d73da85b4f788731524a3
        # save the attached .config to linux build tree
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' O=build_dir ARCH=m68k SHELL=/bin/bash arch/m68k/coldfire/

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 >>)
>> arch/m68k/coldfire/m523x.c:31:19: sparse: sparse: symbol 'm523x_clk_lookup' was not declared. Should it be static?

vim +/m523x_clk_lookup +31 arch/m68k/coldfire/m523x.c

    30	
  > 31	struct clk_lookup m523x_clk_lookup[] = {
    32		CLKDEV_INIT(NULL, "pll.0", &clk_pll),
    33		CLKDEV_INIT(NULL, "sys.0", &clk_sys),
    34		CLKDEV_INIT("mcfpit.0", NULL, &clk_pll),
    35		CLKDEV_INIT("mcfpit.1", NULL, &clk_pll),
    36		CLKDEV_INIT("mcfpit.2", NULL, &clk_pll),
    37		CLKDEV_INIT("mcfpit.3", NULL, &clk_pll),
    38		CLKDEV_INIT("mcfuart.0", NULL, &clk_sys),
    39		CLKDEV_INIT("mcfuart.1", NULL, &clk_sys),
    40		CLKDEV_INIT("mcfuart.2", NULL, &clk_sys),
    41		CLKDEV_INIT("mcfqspi.0", NULL, &clk_sys),
    42		CLKDEV_INIT("fec.0", NULL, &clk_sys),
    43		CLKDEV_INIT("imx1-i2c.0", NULL, &clk_sys),
    44	};
    45	

---
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: 30815 bytes --]

             reply	other threads:[~2021-11-12 19:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-12 19:35 kernel test robot [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-02-11  6:35 arch/m68k/coldfire/m523x.c:31:19: sparse: sparse: symbol 'm523x_clk_lookup' was not declared. Should it be static? kernel test robot
2022-03-21  6:05 kernel test robot
2022-06-07 19:33 kernel test robot
2022-06-08 18:14 kernel test robot

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=202111130330.fhEpFYvX-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=arnd@arndb.de \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-kernel@vger.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