public inbox for [email protected]
 help / color / mirror / Atom feed
From: kernel test robot <[email protected]>
To: Dmitry Osipenko <[email protected]>
Cc: [email protected],
	GNU/Weeb Mailing List <[email protected]>,
	[email protected], Jens Axboe <[email protected]>
Subject: [ammarfaizi2-block:axboe/linux-block/m1/2022-03-01 322/355] drivers/regulator/pfuze100-regulator.c:619:13: error: 'pm_power_off_prepare' undeclared; did you mean 'pfuze_power_off_prepare'?
Date: Wed, 2 Mar 2022 05:34:34 +0800	[thread overview]
Message-ID: <[email protected]> (raw)

tree:   https://github.com/ammarfaizi2/linux-block axboe/linux-block/m1/2022-03-01
head:   d7cc9472c1c5430d7caa806e8180d2359ea46266
commit: 4d1ed10a5e4b5553438f02ca438904fc8c2dcccf [322/355] reboot: Remove pm_power_off_prepare()
config: arc-randconfig-r043-20220301 (https://download.01.org/0day-ci/archive/20220302/[email protected]/config)
compiler: arc-elf-gcc (GCC) 11.2.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://github.com/ammarfaizi2/linux-block/commit/4d1ed10a5e4b5553438f02ca438904fc8c2dcccf
        git remote add ammarfaizi2-block https://github.com/ammarfaizi2/linux-block
        git fetch --no-tags ammarfaizi2-block axboe/linux-block/m1/2022-03-01
        git checkout 4d1ed10a5e4b5553438f02ca438904fc8c2dcccf
        # save the config file to linux build tree
        mkdir build_dir
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross O=build_dir ARCH=arc SHELL=/bin/bash drivers/regulator/

If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <[email protected]>

All errors (new ones prefixed by >>):

   drivers/regulator/pfuze100-regulator.c: In function 'pfuze_power_off_prepare_init':
>> drivers/regulator/pfuze100-regulator.c:619:13: error: 'pm_power_off_prepare' undeclared (first use in this function); did you mean 'pfuze_power_off_prepare'?
     619 |         if (pm_power_off_prepare) {
         |             ^~~~~~~~~~~~~~~~~~~~
         |             pfuze_power_off_prepare
   drivers/regulator/pfuze100-regulator.c:619:13: note: each undeclared identifier is reported only once for each function it appears in
   drivers/regulator/pfuze100-regulator.c: In function 'pfuze100_regulator_remove':
   drivers/regulator/pfuze100-regulator.c:844:17: error: 'pm_power_off_prepare' undeclared (first use in this function); did you mean 'pfuze_power_off_prepare'?
     844 |                 pm_power_off_prepare = NULL;
         |                 ^~~~~~~~~~~~~~~~~~~~
         |                 pfuze_power_off_prepare


vim +619 drivers/regulator/pfuze100-regulator.c

c29daffa322ad36 Oleksij Rempel 2018-08-02  611  
c29daffa322ad36 Oleksij Rempel 2018-08-02  612  static int pfuze_power_off_prepare_init(struct pfuze_chip *pfuze_chip)
c29daffa322ad36 Oleksij Rempel 2018-08-02  613  {
c29daffa322ad36 Oleksij Rempel 2018-08-02  614  	if (pfuze_chip->chip_id != PFUZE100) {
c29daffa322ad36 Oleksij Rempel 2018-08-02  615  		dev_warn(pfuze_chip->dev, "Requested pm_power_off_prepare handler for not supported chip\n");
c29daffa322ad36 Oleksij Rempel 2018-08-02  616  		return -ENODEV;
c29daffa322ad36 Oleksij Rempel 2018-08-02  617  	}
c29daffa322ad36 Oleksij Rempel 2018-08-02  618  
c29daffa322ad36 Oleksij Rempel 2018-08-02 @619  	if (pm_power_off_prepare) {
c29daffa322ad36 Oleksij Rempel 2018-08-02  620  		dev_warn(pfuze_chip->dev, "pm_power_off_prepare is already registered.\n");
c29daffa322ad36 Oleksij Rempel 2018-08-02  621  		return -EBUSY;
c29daffa322ad36 Oleksij Rempel 2018-08-02  622  	}
c29daffa322ad36 Oleksij Rempel 2018-08-02  623  
c29daffa322ad36 Oleksij Rempel 2018-08-02  624  	if (syspm_pfuze_chip) {
c29daffa322ad36 Oleksij Rempel 2018-08-02  625  		dev_warn(pfuze_chip->dev, "syspm_pfuze_chip is already set.\n");
c29daffa322ad36 Oleksij Rempel 2018-08-02  626  		return -EBUSY;
c29daffa322ad36 Oleksij Rempel 2018-08-02  627  	}
c29daffa322ad36 Oleksij Rempel 2018-08-02  628  
c29daffa322ad36 Oleksij Rempel 2018-08-02  629  	syspm_pfuze_chip = pfuze_chip;
c29daffa322ad36 Oleksij Rempel 2018-08-02  630  	pm_power_off_prepare = pfuze_power_off_prepare;
c29daffa322ad36 Oleksij Rempel 2018-08-02  631  
c29daffa322ad36 Oleksij Rempel 2018-08-02  632  	return 0;
c29daffa322ad36 Oleksij Rempel 2018-08-02  633  }
c29daffa322ad36 Oleksij Rempel 2018-08-02  634  

:::::: The code at line 619 was first introduced by commit
:::::: c29daffa322ad36978cbce487f8ebcd9c3c3f7c0 regulator: pfuze100-regulator: provide pm_power_off_prepare handler

:::::: TO: Oleksij Rempel <[email protected]>
:::::: CC: Mark Brown <[email protected]>

---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/[email protected]

                 reply	other threads:[~2022-03-01 21:35 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 \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    /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