linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Douglas Anderson <dianders@chromium.org>
Cc: kbuild-all@lists.01.org,
	Linux Memory Management List <linux-mm@kvack.org>,
	Bjorn Andersson <bjorn.andersson@linaro.org>
Subject: [linux-next:master 4502/10945] drivers/soc/qcom/cpr.c:814:23: error: implicit declaration of function 'nvmem_cell_read_variable_le_u32'
Date: Mon, 30 Aug 2021 00:24:58 +0800	[thread overview]
Message-ID: <202108300053.9pxJdIhi-lkp@intel.com> (raw)

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

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head:   5e63226c72287bc6c6724d4fc7e157af0e3d7908
commit: 6feba6a62c577e98bd9214b73c17860166ac8b91 [4502/10945] PM: AVS: qcom-cpr: Use nvmem_cell_read_variable_le_u32()
config: arm64-randconfig-r011-20210829 (attached as .config)
compiler: aarch64-linux-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://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=6feba6a62c577e98bd9214b73c17860166ac8b91
        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 6feba6a62c577e98bd9214b73c17860166ac8b91
        # save the attached .config to linux build tree
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross ARCH=arm64 

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/soc/qcom/cpr.c: In function 'cpr_populate_ring_osc_idx':
>> drivers/soc/qcom/cpr.c:814:23: error: implicit declaration of function 'nvmem_cell_read_variable_le_u32' [-Werror=implicit-function-declaration]
     814 |                 ret = nvmem_cell_read_variable_le_u32(drv->dev, fuses->ring_osc, &data);
         |                       ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
   cc1: some warnings being treated as errors


vim +/nvmem_cell_read_variable_le_u32 +814 drivers/soc/qcom/cpr.c

   803	
   804	static int
   805	cpr_populate_ring_osc_idx(struct cpr_drv *drv)
   806	{
   807		struct fuse_corner *fuse = drv->fuse_corners;
   808		struct fuse_corner *end = fuse + drv->desc->num_fuse_corners;
   809		const struct cpr_fuse *fuses = drv->cpr_fuses;
   810		u32 data;
   811		int ret;
   812	
   813		for (; fuse < end; fuse++, fuses++) {
 > 814			ret = nvmem_cell_read_variable_le_u32(drv->dev, fuses->ring_osc, &data);
   815			if (ret)
   816				return ret;
   817			fuse->ring_osc_idx = data;
   818		}
   819	
   820		return 0;
   821	}
   822	

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

             reply	other threads:[~2021-08-29 16:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-29 16:24 kernel test robot [this message]
2021-08-30 15:36 ` Doug Anderson

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=202108300053.9pxJdIhi-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=bjorn.andersson@linaro.org \
    --cc=dianders@chromium.org \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-mm@kvack.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