From: kernel test robot <lkp@intel.com>
To: Witold Sadowski <wsadowski@marvell.com>
Cc: oe-kbuild-all@lists.linux.dev,
Linux Memory Management List <linux-mm@kvack.org>,
Mark Brown <broonie@kernel.org>
Subject: [linux-next:master 1008/1677] drivers/spi/spi-cadence-xspi.c:529:33: error: implicit declaration of function 'readq'; did you mean 'readl'?
Date: Tue, 30 Jul 2024 23:31:23 +0800 [thread overview]
Message-ID: <202407302351.yYAIELQC-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: cd19ac2f903276b820f5d0d89de0c896c27036ed
commit: 75128e2a14a9f443e8debdd30445f5934b5a7c83 [1008/1677] spi: cadence: Add Marvell SDMA operations
config: powerpc-randconfig-r023-20230208 (https://download.01.org/0day-ci/archive/20240730/202407302351.yYAIELQC-lkp@intel.com/config)
compiler: powerpc-linux-gcc (GCC) 13.3.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240730/202407302351.yYAIELQC-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/202407302351.yYAIELQC-lkp@intel.com/
All errors (new ones prefixed by >>):
drivers/spi/spi-cadence-xspi.c: In function 'm_ioreadq':
>> drivers/spi/spi-cadence-xspi.c:529:33: error: implicit declaration of function 'readq'; did you mean 'readl'? [-Werror=implicit-function-declaration]
529 | u64 b = readq(addr);
| ^~~~~
| readl
drivers/spi/spi-cadence-xspi.c: In function 'm_iowriteq':
>> drivers/spi/spi-cadence-xspi.c:555:25: error: implicit declaration of function 'writeq'; did you mean 'writel'? [-Werror=implicit-function-declaration]
555 | writeq(*buffer++, addr);
| ^~~~~~
| writel
cc1: some warnings being treated as errors
vim +529 drivers/spi/spi-cadence-xspi.c
518
519 static void m_ioreadq(void __iomem *addr, void *buf, int len)
520 {
521 if (IS_ALIGNED((long)buf, 8) && len >= 8) {
522 u64 full_ops = len / 8;
523 u64 *buffer = buf;
524
525 len -= full_ops * 8;
526 buf += full_ops * 8;
527
528 do {
> 529 u64 b = readq(addr);
530 *buffer++ = b;
531 } while (--full_ops);
532 }
533
534
535 while (len) {
536 u64 tmp_buf;
537
538 tmp_buf = readq(addr);
539 memcpy(buf, &tmp_buf, min(len, 8));
540 len = len > 8 ? len - 8 : 0;
541 buf += 8;
542 }
543 }
544
545 static void m_iowriteq(void __iomem *addr, const void *buf, int len)
546 {
547 if (IS_ALIGNED((long)buf, 8) && len >= 8) {
548 u64 full_ops = len / 8;
549 const u64 *buffer = buf;
550
551 len -= full_ops * 8;
552 buf += full_ops * 8;
553
554 do {
> 555 writeq(*buffer++, addr);
556 } while (--full_ops);
557 }
558
559 while (len) {
560 u64 tmp_buf;
561
562 memcpy(&tmp_buf, buf, min(len, 8));
563 writeq(tmp_buf, addr);
564 len = len > 8 ? len - 8 : 0;
565 buf += 8;
566 }
567 }
568
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-07-30 15:31 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202407302351.yYAIELQC-lkp@intel.com \
--to=lkp@intel.com \
--cc=broonie@kernel.org \
--cc=linux-mm@kvack.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=wsadowski@marvell.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