From: Doug Anderson <dianders@chromium.org>
To: kernel test robot <lkp@intel.com>
Cc: kbuild-all@lists.01.org,
Linux Memory Management List <linux-mm@kvack.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>
Subject: Re: [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 08:36:54 -0700 [thread overview]
Message-ID: <CAD=FV=XNyCZV0Gr8PzsatfUaurMvJpNPmU8GjazKvm3dzdoXqw@mail.gmail.com> (raw)
In-Reply-To: <202108300053.9pxJdIhi-lkp@intel.com>
Hi,
On Sun, Aug 29, 2021 at 9:25 AM kernel test robot <lkp@intel.com> wrote:
>
> 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
Thanks for the report and sorry for the breakage! Should be fixed by:
https://lore.kernel.org/lkml/20210830083449.1.I38e95343209fe1f808c3b4860795a00a2b539701@changeid/
-Doug
prev parent reply other threads:[~2021-08-30 15:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-29 16:24 kernel test robot
2021-08-30 15:36 ` Doug Anderson [this message]
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='CAD=FV=XNyCZV0Gr8PzsatfUaurMvJpNPmU8GjazKvm3dzdoXqw@mail.gmail.com' \
--to=dianders@chromium.org \
--cc=bjorn.andersson@linaro.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.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