From: kernel test robot <lkp@intel.com>
To: Rengarajan S <rengarajan.s@microchip.com>,
unglinuxdriver@microchip.com, broonie@kernel.org,
linux-spi@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: oe-kbuild-all@lists.linux.dev, rengarajan.s@microchip.com
Subject: Re: [PATCH v1 for-next] spi: mchp-pci1xxxx: Updated memcpy implementation for x64 and bcm2711 processors
Date: Thu, 27 Feb 2025 22:00:06 +0800 [thread overview]
Message-ID: <202502272153.zJWKuv3R-lkp@intel.com> (raw)
In-Reply-To: <20250224125153.13728-1-rengarajan.s@microchip.com>
Hi Rengarajan,
kernel test robot noticed the following build errors:
[auto build test ERROR on broonie-spi/for-next]
[also build test ERROR on linus/master v6.14-rc4 next-20250227]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Rengarajan-S/spi-mchp-pci1xxxx-Updated-memcpy-implementation-for-x64-and-bcm2711-processors/20250224-205745
base: https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next
patch link: https://lore.kernel.org/r/20250224125153.13728-1-rengarajan.s%40microchip.com
patch subject: [PATCH v1 for-next] spi: mchp-pci1xxxx: Updated memcpy implementation for x64 and bcm2711 processors
config: sparc-randconfig-001-20250227 (https://download.01.org/0day-ci/archive/20250227/202502272153.zJWKuv3R-lkp@intel.com/config)
compiler: sparc-linux-gcc (GCC) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250227/202502272153.zJWKuv3R-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/202502272153.zJWKuv3R-lkp@intel.com/
All errors (new ones prefixed by >>):
drivers/spi/spi-pci1xxxx.c: In function 'pci1xxxx_spi_write_to_io':
>> drivers/spi/spi-pci1xxxx.c:417:25: error: implicit declaration of function '__raw_writeq'; did you mean '__raw_writel'? [-Wimplicit-function-declaration]
417 | __raw_writeq(*(u64 *)from, to);
| ^~~~~~~~~~~~
| __raw_writel
drivers/spi/spi-pci1xxxx.c: In function 'pci1xxxx_spi_read_from_io':
>> drivers/spi/spi-pci1xxxx.c:448:38: error: implicit declaration of function '__raw_readq'; did you mean '__raw_readl'? [-Wimplicit-function-declaration]
448 | *(u64 *)to = __raw_readq(from);
| ^~~~~~~~~~~
| __raw_readl
vim +417 drivers/spi/spi-pci1xxxx.c
410
411 static void pci1xxxx_spi_write_to_io(void __iomem *to, const void *from,
412 size_t count, size_t size)
413 {
414 while (count) {
415 if (size == 8 && (IS_ALIGNED((unsigned long)to, 8)) &&
416 count >= 8) {
> 417 __raw_writeq(*(u64 *)from, to);
418 from += 8;
419 to += 8;
420 count -= 8;
421 } else if (size >= 4 && (IS_ALIGNED((unsigned long)to, 4)) &&
422 count >= 4) {
423 __raw_writel(*(u32 *)from, to);
424 from += 4;
425 to += 4;
426 count -= 4;
427 } else if (size >= 2 && (IS_ALIGNED((unsigned long)to, 2)) &&
428 count >= 2) {
429 __raw_writew(*(u16 *)from, to);
430 from += 2;
431 to += 2;
432 count -= 2;
433 } else {
434 __raw_writeb(*(u8 *)from, to);
435 from += 1;
436 to += 1;
437 count -= 1;
438 }
439 }
440 }
441
442 static void pci1xxxx_spi_read_from_io(void *to, const void __iomem *from,
443 size_t count, size_t size)
444 {
445 while (count) {
446 if (size == 8 && (IS_ALIGNED((unsigned long)from, 8)) &&
447 count >= 8) {
> 448 *(u64 *)to = __raw_readq(from);
449 from += 8;
450 to += 8;
451 count -= 8;
452 } else if (size >= 4 && (IS_ALIGNED((unsigned long)from, 4)) &&
453 count >= 4) {
454 *(u32 *)to = __raw_readl(from);
455 from += 4;
456 to += 4;
457 count -= 4;
458 } else if (size >= 2 && (IS_ALIGNED((unsigned long)from, 2)) &&
459 count >= 2) {
460 *(u16 *)to = __raw_readw(from);
461 from += 2;
462 to += 2;
463 count -= 2;
464 } else {
465 *(u8 *)to = __raw_readb(from);
466 from += 1;
467 to += 1;
468 count -= 1;
469 }
470 }
471 }
472
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2025-02-27 14:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-24 12:51 [PATCH v1 for-next] spi: mchp-pci1xxxx: Updated memcpy implementation for x64 and bcm2711 processors Rengarajan S
2025-02-24 14:30 ` Mark Brown
2025-03-19 13:58 ` Rengarajan.S
2025-03-19 14:33 ` Mark Brown
2025-02-27 14:00 ` kernel test robot [this message]
2025-02-27 19:50 ` kernel 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=202502272153.zJWKuv3R-lkp@intel.com \
--to=lkp@intel.com \
--cc=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=rengarajan.s@microchip.com \
--cc=unglinuxdriver@microchip.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