From: Nandor Han <nandor.han@vaisala.com>
To: unlisted-recipients:; (no To-header on input)
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org,
Sebastian Reichel <sre@kernel.org>
Subject: Re: drivers/power/reset/nvmem-reboot-mode.c:27:42: error: passing argument 2 of 'nvmem_cell_write' from incompatible pointer type
Date: Mon, 12 Aug 2019 15:41:42 +0300 [thread overview]
Message-ID: <03e59e9b-8647-c9b2-b60a-99817af5313d@vaisala.com> (raw)
In-Reply-To: <201908110745.3Zksfatm%lkp@intel.com>
On 8/11/19 2:43 AM, kbuild test robot wrote:
> Hi Han,
>
> FYI, the error/warning still remains.
>
> tree: https://kernel.googlesource.com/pub/scm/linux/kernel/git/torvalds/linux.git master
> head: dcbb4a153971ff8646af0c963f5698bf21bfbfdc
> commit: 7a78a7f7695bf9ef9cef3c06fbc5fa4573fd0eef power: reset: nvmem-reboot-mode: use NVMEM as reboot mode write interface
> date: 7 weeks ago
> config: x86_64-randconfig-d003-201932 (attached as .config)
> compiler: gcc-7 (Debian 7.4.0-10) 7.4.0
> reproduce:
> git checkout 7a78a7f7695bf9ef9cef3c06fbc5fa4573fd0eef
> # save the attached .config to linux build tree
> make ARCH=x86_64
>
> If you fix the issue, kindly add following tag
> Reported-by: kbuild test robot <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:42: error: passing argument 2 of 'nvmem_cell_write' from incompatible pointer type [-Werror=incompatible-pointer-types]
> ret = nvmem_cell_write(nvmem_rbm->cell, &magic, sizeof(magic));
> ^
> In file included from drivers/power/reset/nvmem-reboot-mode.c:10:0:
> include/linux/nvmem-consumer.h:120:19: note: expected 'const char *' but argument is of type 'unsigned int *'
> static inline int nvmem_cell_write(struct nvmem_cell *cell,
> ^~~~~~~~~~~~~~~~
> cc1: some warnings being treated as errors
>
> vim +/nvmem_cell_write +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(nvmem_rbm->cell, &magic, sizeof(magic));
> 28 if (ret < 0)
> 29 dev_err(reboot->dev, "update reboot mode bits failed\n");
> 30
> 31 return ret;
> 32 }
> 33
>
> ---
> 0-DAY kernel test infrastructure Open Source Technology Center
> https://lists.01.org/pipermail/kbuild-all Intel Corporation
>
Hi,
Seems that `nvmem-consumer.h` declares a different signature for
`nvmem_cell_write` method depending on `CONFIG_NVMEM` configuration:
#if IS_ENABLED(CONFIG_NVMEM)
...
int nvmem_cell_write(struct nvmem_cell *cell, void *buf, size_t len);
...
#else
...
static inline int nvmem_cell_write(struct nvmem_cell *cell,
const char *buf, size_t len)
{
return -EOPNOTSUPP;
}
...
#endif /* CONFIG_NVMEM *
What's the best approach here?
Nandor
next prev parent reply other threads:[~2019-08-12 12:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-10 23:43 kbuild test robot
2019-08-12 12:41 ` Nandor Han [this message]
2019-09-08 0:40 kbuild test robot
2019-09-11 8:22 kbuild test robot
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=03e59e9b-8647-c9b2-b60a-99817af5313d@vaisala.com \
--to=nandor.han@vaisala.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sre@kernel.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®