From: kernel test robot <lkp@intel.com>
To: Jennifer Berringer <jberring@redhat.com>,
Srinivas Kandagatla <srinivas.kandagatla@linaro.org>,
Sebastian Reichel <sre@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Maxime Ripard <mripard@kernel.org>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
linux-pm@vger.kernel.org,
Jennifer Berringer <jberring@redhat.com>
Subject: Re: [PATCH 3/3] power: reset: nvmem-reboot-mode: fix write for small cells
Date: Sat, 19 Oct 2024 08:26:26 +0800 [thread overview]
Message-ID: <202410190829.e98plEvU-lkp@intel.com> (raw)
In-Reply-To: <20241017160904.2803663-3-jberring@redhat.com>
Hi Jennifer,
kernel test robot noticed the following build errors:
[auto build test ERROR on 98f7e32f20d28ec452afb208f9cffc08448a2652]
url: https://github.com/intel-lab-lkp/linux/commits/Jennifer-Berringer/nvmem-core-add-nvmem_cell_write_variable_u32/20241018-001140
base: 98f7e32f20d28ec452afb208f9cffc08448a2652
patch link: https://lore.kernel.org/r/20241017160904.2803663-3-jberring%40redhat.com
patch subject: [PATCH 3/3] power: reset: nvmem-reboot-mode: fix write for small cells
config: i386-randconfig-015-20241019 (https://download.01.org/0day-ci/archive/20241019/202410190829.e98plEvU-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20241019/202410190829.e98plEvU-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202410190829.e98plEvU-lkp@intel.com/
All errors (new ones prefixed by >>):
drivers/power/reset/nvmem-reboot-mode.c: In function 'nvmem_reboot_mode_write':
>> drivers/power/reset/nvmem-reboot-mode.c:27:15: error: implicit declaration of function 'nvmem_cell_write_variable_u32'; did you mean 'nvmem_cell_read_variable_le_u32'? [-Werror=implicit-function-declaration]
27 | ret = nvmem_cell_write_variable_u32(nvmem_rbm->cell, magic);
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~
| nvmem_cell_read_variable_le_u32
cc1: some warnings being treated as errors
vim +27 drivers/power/reset/nvmem-reboot-mode.c
18
19 static int nvmem_reboot_mode_write(struct reboot_mode_driver *reboot,
20 unsigned int magic)
21 {
22 int ret;
23 struct nvmem_reboot_mode *nvmem_rbm;
24
25 nvmem_rbm = container_of(reboot, struct nvmem_reboot_mode, reboot);
26
> 27 ret = nvmem_cell_write_variable_u32(nvmem_rbm->cell, magic);
28 if (ret < 0)
29 dev_err(reboot->dev, "update reboot mode bits failed\n");
30
31 return ret;
32 }
33
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2024-10-19 0:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-17 16:09 [PATCH 1/3] nvmem: core: improve range check for nvmem_cell_write() Jennifer Berringer
2024-10-17 16:09 ` [PATCH 2/3] nvmem: core: add nvmem_cell_write_variable_u32() Jennifer Berringer
2024-10-17 16:09 ` [PATCH 3/3] power: reset: nvmem-reboot-mode: fix write for small cells Jennifer Berringer
2024-10-19 0:26 ` kernel test robot [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=202410190829.e98plEvU-lkp@intel.com \
--to=lkp@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=jberring@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mripard@kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=sre@kernel.org \
--cc=srinivas.kandagatla@linaro.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
all inboxes | Powered by JetHome®