linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Kate Hsuan <hpa@redhat.com>
Cc: kbuild-all@lists.01.org,
	Linux Memory Management List <linux-mm@kvack.org>,
	Sebastian Reichel <sebastian.reichel@collabora.com>,
	Hans de Goede <hdegoede@redhat.com>
Subject: [linux-next:master 6417/11322] drivers/power/supply/axp288_charger.c:411:8: error: implicit declaration of function 'iosf_mbi_block_punit_i2c_access'
Date: Tue, 26 Oct 2021 14:41:55 +0800	[thread overview]
Message-ID: <202110261445.ekxGWWon-lkp@intel.com> (raw)

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

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head:   9ae1fbdeabd3b3f668ad0bcb47d64b3a9fb4f8fc
commit: ed229454856e565c5a7d3287cbc63f2cf077b34f [6417/11322] power: supply: axp288-charger: Optimize register reading method
config: x86_64-randconfig-a004-20211004 (attached as .config)
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
reproduce (this is a W=1 build):
        # https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=ed229454856e565c5a7d3287cbc63f2cf077b34f
        git remote add linux-next https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
        git fetch --no-tags linux-next master
        git checkout ed229454856e565c5a7d3287cbc63f2cf077b34f
        # save the attached .config to linux build tree
        make W=1 ARCH=x86_64 

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

Note: the linux-next/master HEAD 9ae1fbdeabd3b3f668ad0bcb47d64b3a9fb4f8fc builds fine.
      It may have been fixed somewhere.

All errors (new ones prefixed by >>):

   drivers/power/supply/axp288_charger.c: In function 'axp288_charger_usb_update_property':
>> drivers/power/supply/axp288_charger.c:411:8: error: implicit declaration of function 'iosf_mbi_block_punit_i2c_access' [-Werror=implicit-function-declaration]
     411 |  ret = iosf_mbi_block_punit_i2c_access();
         |        ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>> drivers/power/supply/axp288_charger.c:430:2: error: implicit declaration of function 'iosf_mbi_unblock_punit_i2c_access' [-Werror=implicit-function-declaration]
     430 |  iosf_mbi_unblock_punit_i2c_access();
         |  ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
   cc1: some warnings being treated as errors


vim +/iosf_mbi_block_punit_i2c_access +411 drivers/power/supply/axp288_charger.c

   401	
   402	static int axp288_charger_usb_update_property(struct axp288_chrg_info *info)
   403	{
   404		int ret = 0;
   405	
   406		if (info->valid && time_before(jiffies, info->last_updated + AXP288_REG_UPDATE_INTERVAL))
   407			return 0;
   408	
   409		dev_dbg(&info->pdev->dev, "Charger updating register values...\n");
   410	
 > 411		ret = iosf_mbi_block_punit_i2c_access();
   412		if (ret < 0)
   413			return ret;
   414	
   415		ret = axp288_charger_reg_readb(info, AXP20X_PWR_INPUT_STATUS, &info->input_status);
   416		if (ret < 0)
   417			goto out;
   418	
   419		ret = axp288_charger_reg_readb(info, AXP20X_PWR_OP_MODE, &info->op_mode);
   420		if (ret < 0)
   421			goto out;
   422	
   423		ret = axp288_charger_reg_readb(info, AXP20X_CHRG_BAK_CTRL, &info->backend_control);
   424		if (ret < 0)
   425			goto out;
   426	
   427		info->last_updated = jiffies;
   428		info->valid = true;
   429	out:
 > 430		iosf_mbi_unblock_punit_i2c_access();
   431		return ret;
   432	}
   433	

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

                 reply	other threads:[~2021-10-26  6:42 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=202110261445.ekxGWWon-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=hdegoede@redhat.com \
    --cc=hpa@redhat.com \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-mm@kvack.org \
    --cc=sebastian.reichel@collabora.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;
as well as URLs for NNTP newsgroup(s).