From: Wolfram Sang <wsa-dev@sang-engineering.com>
To: kernel test robot <lkp@intel.com>
Cc: oe-kbuild-all@lists.linux.dev
Subject: Re: [wsa:renesas/g3s/i3c 7/19] drivers/i3c/internals.h:35:9: error: implicit declaration of function 'writesl'
Date: Tue, 15 Jul 2025 22:59:57 +0200 [thread overview]
Message-ID: <aHbBTY5gJ15B-x98@shikoro> (raw)
In-Reply-To: <202507150208.BZDzzJ5E-lkp@intel.com>
> config: x86_64-buildonly-randconfig-003-20250714 (https://download.01.org/0day-ci/archive/20250715/202507150208.BZDzzJ5E-lkp@intel.com/config)
I can't reproduce this with the above 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)
> >> drivers/i3c/internals.h:40:17: error: implicit declaration of function 'writel' [-Werror=implicit-function-declaration]
> 40 | writel(tmp, addr);
> | ^~~~~~
But I added the 'linux/io.h' header to internals.h and will let the bot
recheck my branch...
prev parent reply other threads:[~2025-07-15 20:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-14 18:49 [wsa:renesas/g3s/i3c 7/19] drivers/i3c/internals.h:35:9: error: implicit declaration of function 'writesl' kernel test robot
2025-07-15 20:59 ` Wolfram Sang [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=aHbBTY5gJ15B-x98@shikoro \
--to=wsa-dev@sang-engineering.com \
--cc=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
/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.