From: kernel test robot <lkp@intel.com>
To: Wolfram Sang <wsa-dev@sang-engineering.com>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [wsa:renesas/g3s/i3c 7/19] drivers/i3c/internals.h:35:9: error: implicit declaration of function 'writesl'
Date: Tue, 15 Jul 2025 02:49:17 +0800 [thread overview]
Message-ID: <202507150208.BZDzzJ5E-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/wsa/linux.git renesas/g3s/i3c
head: 96358bcce0f6b8c20c9453ca17d3ad1d16515fd4
commit: 8af3723cb0b4ec9f1f4442b617b1990ec0302c8e [7/19] i3c: master: Add inline i3c_readl_fifo() and i3c_writel_fifo()
config: x86_64-buildonly-randconfig-003-20250714 (https://download.01.org/0day-ci/archive/20250715/202507150208.BZDzzJ5E-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14+deb12u1) 12.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250715/202507150208.BZDzzJ5E-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/202507150208.BZDzzJ5E-lkp@intel.com/
All errors (new ones prefixed by >>):
In file included from drivers/i3c/master.c:21:
drivers/i3c/internals.h: In function 'i3c_writel_fifo':
>> drivers/i3c/internals.h:35:9: error: implicit declaration of function 'writesl' [-Werror=implicit-function-declaration]
35 | writesl(addr, buf, nbytes / 4);
| ^~~~~~~
>> drivers/i3c/internals.h:40:17: error: implicit declaration of function 'writel' [-Werror=implicit-function-declaration]
40 | writel(tmp, addr);
| ^~~~~~
drivers/i3c/internals.h: In function 'i3c_readl_fifo':
>> drivers/i3c/internals.h:53:9: error: implicit declaration of function 'readsl' [-Werror=implicit-function-declaration]
53 | readsl(addr, buf, nbytes / 4);
| ^~~~~~
>> drivers/i3c/internals.h:57:23: error: implicit declaration of function 'readl' [-Werror=implicit-function-declaration]
57 | tmp = readl(addr);
| ^~~~~
cc1: some warnings being treated as errors
vim +/writesl +35 drivers/i3c/internals.h
25
26 /**
27 * i3c_writel_fifo - Write data buffer to 32bit FIFO
28 * @addr: FIFO Address to write to
29 * @buf: Pointer to the data bytes to write
30 * @nbytes: Number of bytes to write
31 */
32 static inline void i3c_writel_fifo(void __iomem *addr, const void *buf,
33 int nbytes)
34 {
> 35 writesl(addr, buf, nbytes / 4);
36 if (nbytes & 3) {
37 u32 tmp = 0;
38
39 memcpy(&tmp, buf + (nbytes & ~3), nbytes & 3);
> 40 writel(tmp, addr);
41 }
42 }
43
44 /**
45 * i3c_readl_fifo - Read data buffer from 32bit FIFO
46 * @addr: FIFO Address to read from
47 * @buf: Pointer to the buffer to store read bytes
48 * @nbytes: Number of bytes to read
49 */
50 static inline void i3c_readl_fifo(const void __iomem *addr, void *buf,
51 int nbytes)
52 {
> 53 readsl(addr, buf, nbytes / 4);
54 if (nbytes & 3) {
55 u32 tmp;
56
> 57 tmp = readl(addr);
58 memcpy(buf + (nbytes & ~3), &tmp, nbytes & 3);
59 }
60 }
61
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2025-07-14 18:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-14 18:49 kernel test robot [this message]
2025-07-15 20:59 ` [wsa:renesas/g3s/i3c 7/19] drivers/i3c/internals.h:35:9: error: implicit declaration of function 'writesl' Wolfram Sang
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=202507150208.BZDzzJ5E-lkp@intel.com \
--to=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=wsa-dev@sang-engineering.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.