linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Adrian Hunter <adrian.hunter@intel.com>
Cc: llvm@lists.linux.dev, kbuild-all@lists.01.org,
	Linux Memory Management List <linux-mm@kvack.org>,
	"Martin K. Petersen" <martin.petersen@oracle.com>,
	Avri Altman <avri.altman@wdc.com>
Subject: [linux-next:master 8710/9200] drivers/scsi/ufs/ufshcd-pci.c:459:9: error: implicit declaration of function 'ufshcd_system_resume'
Date: Mon, 18 Oct 2021 21:40:13 +0800	[thread overview]
Message-ID: <202110182103.VCwmBYpy-lkp@intel.com> (raw)

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

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head:   60e8840126bdcb60bccef74c3f962742183c681f
commit: 21431d5bdf1523301e70ec7071dcbf7effd4e988 [8710/9200] scsi: core: ufs-pci: Force a full restore after suspend-to-disk
config: i386-randconfig-r016-20211018 (attached as .config)
compiler: clang version 14.0.0 (https://github.com/llvm/llvm-project d245f2e8597bfb52c34810a328d42b990e4af1a4)
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/next/linux-next.git/commit/?id=21431d5bdf1523301e70ec7071dcbf7effd4e988
        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 21431d5bdf1523301e70ec7071dcbf7effd4e988
        # save the attached .config to linux build tree
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 ARCH=i386 

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/scsi/ufs/ufshcd-pci.c:459:9: error: implicit declaration of function 'ufshcd_system_resume' [-Werror,-Wimplicit-function-declaration]
           return ufshcd_system_resume(dev);
                  ^
   drivers/scsi/ufs/ufshcd-pci.c:459:9: note: did you mean 'ufshcd_vops_resume'?
   drivers/scsi/ufs/ufshcd.h:1331:19: note: 'ufshcd_vops_resume' declared here
   static inline int ufshcd_vops_resume(struct ufs_hba *hba, enum ufs_pm_op op)
                     ^
   1 error generated.


vim +/ufshcd_system_resume +459 drivers/scsi/ufs/ufshcd-pci.c

   451	
   452	static int ufshcd_pci_restore(struct device *dev)
   453	{
   454		struct ufs_hba *hba = dev_get_drvdata(dev);
   455	
   456		/* Force a full reset and restore */
   457		ufshcd_set_link_off(hba);
   458	
 > 459		return ufshcd_system_resume(dev);
   460	}
   461	

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

                 reply	other threads:[~2021-10-18 13:40 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=202110182103.VCwmBYpy-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=adrian.hunter@intel.com \
    --cc=avri.altman@wdc.com \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-mm@kvack.org \
    --cc=llvm@lists.linux.dev \
    --cc=martin.petersen@oracle.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