linux-arm-kernel.lists.infradead.org archive mirror
 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-arm-kernel@lists.infradead.org,
	Linus Walleij <linus.walleij@linaro.org>
Subject: [nomadik:ixp4xx-cleanup-v5.13-rc1 18/24] drivers/watchdog/ixp4xx_wdt.c:175:8: error: implicit declaration of function 'read_cpuid_id'
Date: Wed, 2 Jun 2021 00:06:54 +0800	[thread overview]
Message-ID: <202106020046.GC9VsqP8-lkp@intel.com> (raw)

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

Hi Arnd,

First bad commit (maybe != root cause):

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-nomadik.git ixp4xx-cleanup-v5.13-rc1
head:   c207fa412ab2848ee0539511ad8eed7aafe626a4
commit: c063af2315e30ac4defc8b59983f972c326649f4 [18/24] watchdog: ixp4xx: move mmio access to timer driver
config: m68k-allmodconfig (attached as .config)
compiler: m68k-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
        # https://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-nomadik.git/commit/?id=c063af2315e30ac4defc8b59983f972c326649f4
        git remote add nomadik https://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-nomadik.git
        git fetch --no-tags nomadik ixp4xx-cleanup-v5.13-rc1
        git checkout c063af2315e30ac4defc8b59983f972c326649f4
        # save the attached .config to linux build tree
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=m68k 

If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>

All errors (new ones prefixed by >>):

   drivers/watchdog/ixp4xx_wdt.c: In function 'ixp4xx_wdt_init':
>> drivers/watchdog/ixp4xx_wdt.c:175:8: error: implicit declaration of function 'read_cpuid_id' [-Werror=implicit-function-declaration]
     175 |  if (!(read_cpuid_id() & 0xf) && !cpu_is_ixp46x()) {
         |        ^~~~~~~~~~~~~
   cc1: some warnings being treated as errors


vim +/read_cpuid_id +175 drivers/watchdog/ixp4xx_wdt.c

^1da177e4c3f41 drivers/char/watchdog/ixp4xx_wdt.c Linus Torvalds 2005-04-16  164  
^1da177e4c3f41 drivers/char/watchdog/ixp4xx_wdt.c Linus Torvalds 2005-04-16  165  static int __init ixp4xx_wdt_init(void)
^1da177e4c3f41 drivers/char/watchdog/ixp4xx_wdt.c Linus Torvalds 2005-04-16  166  {
^1da177e4c3f41 drivers/char/watchdog/ixp4xx_wdt.c Linus Torvalds 2005-04-16  167  	int ret;
^1da177e4c3f41 drivers/char/watchdog/ixp4xx_wdt.c Linus Torvalds 2005-04-16  168  
c063af2315e30a drivers/watchdog/ixp4xx_wdt.c      Arnd Bergmann  2019-08-26  169  	ret = ixp4xx_boot_status();
c063af2315e30a drivers/watchdog/ixp4xx_wdt.c      Arnd Bergmann  2019-08-26  170  	if (ret < 0)
c063af2315e30a drivers/watchdog/ixp4xx_wdt.c      Arnd Bergmann  2019-08-26  171  		return ret;
c063af2315e30a drivers/watchdog/ixp4xx_wdt.c      Arnd Bergmann  2019-08-26  172  
c063af2315e30a drivers/watchdog/ixp4xx_wdt.c      Arnd Bergmann  2019-08-26  173  	boot_status = ret ?  WDIOF_CARDRESET : 0;
c063af2315e30a drivers/watchdog/ixp4xx_wdt.c      Arnd Bergmann  2019-08-26  174  
0ba8b9b273c45d drivers/watchdog/ixp4xx_wdt.c      Russell King   2008-08-10 @175  	if (!(read_cpuid_id() & 0xf) && !cpu_is_ixp46x()) {
27c766aaacb265 drivers/watchdog/ixp4xx_wdt.c      Joe Perches    2012-02-15  176  		pr_err("Rev. A0 IXP42x CPU detected - watchdog disabled\n");
^1da177e4c3f41 drivers/char/watchdog/ixp4xx_wdt.c Linus Torvalds 2005-04-16  177  
^1da177e4c3f41 drivers/char/watchdog/ixp4xx_wdt.c Linus Torvalds 2005-04-16  178  		return -ENODEV;
^1da177e4c3f41 drivers/char/watchdog/ixp4xx_wdt.c Linus Torvalds 2005-04-16  179  	}
^1da177e4c3f41 drivers/char/watchdog/ixp4xx_wdt.c Linus Torvalds 2005-04-16  180  	ret = misc_register(&ixp4xx_wdt_miscdev);
^1da177e4c3f41 drivers/char/watchdog/ixp4xx_wdt.c Linus Torvalds 2005-04-16  181  	if (ret == 0)
27c766aaacb265 drivers/watchdog/ixp4xx_wdt.c      Joe Perches    2012-02-15  182  		pr_info("timer heartbeat %d sec\n", heartbeat);
^1da177e4c3f41 drivers/char/watchdog/ixp4xx_wdt.c Linus Torvalds 2005-04-16  183  	return ret;
^1da177e4c3f41 drivers/char/watchdog/ixp4xx_wdt.c Linus Torvalds 2005-04-16  184  }
^1da177e4c3f41 drivers/char/watchdog/ixp4xx_wdt.c Linus Torvalds 2005-04-16  185  

:::::: The code at line 175 was first introduced by commit
:::::: 0ba8b9b273c45dd23f60ff700e265a0069b33758 [ARM] cputype: separate definitions, use them

:::::: TO: Russell King <rmk@dyn-67.arm.linux.org.uk>
:::::: CC: Russell King <rmk+kernel@arm.linux.org.uk>

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

[-- Attachment #3: Type: text/plain, Size: 176 bytes --]

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

                 reply	other threads:[~2021-06-01 16: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=202106020046.GC9VsqP8-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=arnd@arndb.de \
    --cc=kbuild-all@lists.01.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).