From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: Re: [RFC PATCH 02/14] coresight: Introduce device access abstraction
Date: Thu, 30 Jul 2020 04:56:41 +0800 [thread overview]
Message-ID: <202007300427.kO0zle7x%lkp@intel.com> (raw)
In-Reply-To: <20200722172040.1299289-3-suzuki.poulose@arm.com>
[-- Attachment #1: Type: text/plain, Size: 6548 bytes --]
Hi Suzuki,
[FYI, it's a private test report for your RFC patch.]
[auto build test ERROR on next-20200722]
[also build test ERROR on v5.8-rc7]
[cannot apply to stm32/stm32-next keystone/next rockchip/for-next shawnguo/for-next soc/for-next linus/master v5.8-rc6 v5.8-rc5 v5.8-rc4]
[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]
url: https://github.com/0day-ci/linux/commits/Suzuki-K-Poulose/coresight-Support-for-ETMv4-4-system-instructions/20200723-012330
base: 73aece61f643fc0a1d224b6ad53e70832ac757c3
config: i386-randconfig-a013-20200729 (attached as .config)
compiler: gcc-9 (Debian 9.3.0-14) 9.3.0
reproduce (this is a W=1 build):
# save the attached .config to linux build tree
make W=1 ARCH=i386
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
In file included from drivers/misc/habanalabs/goya/goya_coresight.c:15:
include/linux/coresight.h: In function 'csdev_access_relaxed_read64':
include/linux/coresight.h:369:10: error: implicit declaration of function 'readq_relaxed'; did you mean 'readw_relaxed'? [-Werror=implicit-function-declaration]
369 | return readq_relaxed(csa->base + offset);
| ^~~~~~~~~~~~~
| readw_relaxed
include/linux/coresight.h: In function 'csdev_access_read64':
include/linux/coresight.h:383:10: error: implicit declaration of function 'readq'; did you mean 'readl'? [-Werror=implicit-function-declaration]
383 | return readq(csa->base + offset);
| ^~~~~
| readl
include/linux/coresight.h: In function 'csdev_access_relaxed_write64':
include/linux/coresight.h:402:10: error: implicit declaration of function 'writeq_relaxed'; did you mean 'writel_relaxed'? [-Werror=implicit-function-declaration]
402 | return writeq_relaxed(val, csa->base + offset);
| ^~~~~~~~~~~~~~
| writel_relaxed
include/linux/coresight.h:402:10: warning: 'return' with a value, in function returning void [-Wreturn-type]
402 | return writeq_relaxed(val, csa->base + offset);
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
include/linux/coresight.h:397:20: note: declared here
397 | static inline void csdev_access_relaxed_write64(struct csdev_access *csa,
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~
include/linux/coresight.h: In function 'csdev_access_write64':
include/linux/coresight.h:418:10: error: implicit declaration of function 'writeq'; did you mean 'writel'? [-Werror=implicit-function-declaration]
418 | return writeq(val, csa->base + offset);
| ^~~~~~
| writel
include/linux/coresight.h:418:10: warning: 'return' with a value, in function returning void [-Wreturn-type]
418 | return writeq(val, csa->base + offset);
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
include/linux/coresight.h:415:20: note: declared here
415 | static inline void csdev_access_write64(struct csdev_access *csa, u64 val, u32 offset)
| ^~~~~~~~~~~~~~~~~~~~
include/linux/coresight.h: At top level:
include/linux/coresight.h:501:1: error: expected identifier or '(' before '{' token
501 | {
| ^
include/linux/coresight.h:504:19: error: static declaration of 'coresight_relaxed_read64' follows non-static declaration
504 | static inline u64 coresight_relaxed_read64(struct coresight_device *csdev,
| ^~~~~~~~~~~~~~~~~~~~~~~~
include/linux/coresight.h:424:5: note: previous declaration of 'coresight_relaxed_read64' was here
424 | u64 coresight_relaxed_read64(struct coresight_device *csdev, u32 offset);
| ^~~~~~~~~~~~~~~~~~~~~~~~
>> include/linux/coresight.h:511:19: error: static declaration of 'coresight_read64' follows non-static declaration
511 | static inline u64 coresight_read64(struct coresight_device *csdev, u32 offset)
| ^~~~~~~~~~~~~~~~
include/linux/coresight.h:425:5: note: previous declaration of 'coresight_read64' was here
425 | u64 coresight_read64(struct coresight_device *csdev, u32 offset);
| ^~~~~~~~~~~~~~~~
>> include/linux/coresight.h:517:20: error: static declaration of 'coresight_relaxed_write64' follows non-static declaration
517 | static inline void coresight_relaxed_write64(struct coresight_device *csdev,
| ^~~~~~~~~~~~~~~~~~~~~~~~~
include/linux/coresight.h:426:6: note: previous declaration of 'coresight_relaxed_write64' was here
426 | void coresight_relaxed_write64(struct coresight_device *csdev,
| ^~~~~~~~~~~~~~~~~~~~~~~~~
include/linux/coresight.h:523:20: error: static declaration of 'coresight_write64' follows non-static declaration
523 | static inline void coresight_write64(struct coresight_device *csdev, u64 val, u32 offset)
| ^~~~~~~~~~~~~~~~~
include/linux/coresight.h:428:6: note: previous declaration of 'coresight_write64' was here
428 | void coresight_write64(struct coresight_device *csdev, u64 val, u32 offset);
| ^~~~~~~~~~~~~~~~~
include/linux/coresight.h:499:13: warning: 'coresight_relaxed_write32' declared 'static' but never defined [-Wunused-function]
499 | static void coresight_relaxed_write32(struct coresight_device *csdev,
| ^~~~~~~~~~~~~~~~~~~~~~~~~
include/linux/coresight.h:495:13: warning: 'coresight_write32' defined but not used [-Wunused-function]
495 | static void coresight_write32(struct coresight_device *csdev, u32 val, u32 offset)
| ^~~~~~~~~~~~~~~~~
cc1: some warnings being treated as errors
vim +/coresight_read64 +511 include/linux/coresight.h
510
> 511 static inline u64 coresight_read64(struct coresight_device *csdev, u32 offset)
512 {
513 WARN_ON_ONCE(1);
514 return 0;
515 }
516
> 517 static inline void coresight_relaxed_write64(struct coresight_device *csdev,
518 u64 val,
519 u32 offset)
520 {
521 }
522
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org
[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 46776 bytes --]
next prev parent reply other threads:[~2020-07-29 20:56 UTC|newest]
Thread overview: 75+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-22 17:20 [RFC PATCH 00/14] coresight: Support for ETMv4.4 system instructions Suzuki K Poulose
2020-07-22 17:20 ` Suzuki K Poulose
2020-07-22 17:20 ` [RFC PATCH 01/14] coresight: etm4x: Skip save/restore before device registration Suzuki K Poulose
2020-07-22 17:20 ` Suzuki K Poulose
2020-07-29 18:01 ` Mathieu Poirier
2020-07-29 18:01 ` Mathieu Poirier
2020-07-30 14:45 ` Suzuki K Poulose
2020-07-30 14:45 ` Suzuki K Poulose
2020-07-22 17:20 ` [RFC PATCH 02/14] coresight: Introduce device access abstraction Suzuki K Poulose
2020-07-22 17:20 ` Suzuki K Poulose
2020-07-24 4:40 ` kernel test robot
2020-07-29 19:56 ` Mathieu Poirier
2020-07-29 19:56 ` Mathieu Poirier
2020-07-30 14:58 ` Suzuki K Poulose
2020-07-30 14:58 ` Suzuki K Poulose
2020-07-29 20:56 ` kernel test robot [this message]
2020-07-22 17:20 ` [RFC PATCH 03/14] coresight: tpiu: Use coresight " Suzuki K Poulose
2020-07-22 17:20 ` Suzuki K Poulose
2020-07-29 21:01 ` Mathieu Poirier
2020-07-29 21:01 ` Mathieu Poirier
2020-07-31 11:36 ` Suzuki K Poulose
2020-07-31 11:36 ` Suzuki K Poulose
2020-07-22 17:20 ` [RFC PATCH 04/14] coresight: etm4x: Free up argument of etm4_init_arch_data Suzuki K Poulose
2020-07-22 17:20 ` Suzuki K Poulose
2020-07-30 17:31 ` Mathieu Poirier
2020-07-30 17:31 ` Mathieu Poirier
2020-07-31 9:39 ` Suzuki K Poulose
2020-07-31 9:39 ` Suzuki K Poulose
2020-07-22 17:20 ` [RFC PATCH 05/14] coresight: Convert coresight_timeout to use access abstraction Suzuki K Poulose
2020-07-22 17:20 ` Suzuki K Poulose
2020-07-30 18:00 ` Mathieu Poirier
2020-07-30 18:00 ` Mathieu Poirier
2020-07-22 17:20 ` [RFC PATCH 06/14] coresight: Convert claim and lock operations to use access wrappers Suzuki K Poulose
2020-07-22 17:20 ` Suzuki K Poulose
2020-07-27 6:04 ` kernel test robot
2020-07-27 17:56 ` kernel test robot
2020-07-28 9:47 ` Suzuki K Poulose
2020-07-30 19:54 ` Mathieu Poirier
2020-07-30 19:54 ` Mathieu Poirier
2020-07-31 9:46 ` Suzuki K Poulose
2020-07-31 9:46 ` Suzuki K Poulose
2020-07-22 17:20 ` [RFC PATCH 07/14] coresight: etm4x: Always read the registers on the host CPU Suzuki K Poulose
2020-07-22 17:20 ` Suzuki K Poulose
2020-07-30 19:56 ` Mathieu Poirier
2020-07-30 19:56 ` Mathieu Poirier
2020-07-22 17:20 ` [RFC PATCH 08/14] coresight: etm4x: Convert all register accesses Suzuki K Poulose
2020-07-22 17:20 ` Suzuki K Poulose
2020-07-30 20:20 ` Mathieu Poirier
2020-07-30 20:20 ` Mathieu Poirier
2020-07-31 9:49 ` Suzuki K Poulose
2020-07-31 9:49 ` Suzuki K Poulose
2020-07-22 17:20 ` [RFC PATCH 09/14] coresight: etm4x: Add sysreg access helpers Suzuki K Poulose
2020-07-22 17:20 ` Suzuki K Poulose
2020-07-30 21:41 ` Mathieu Poirier
2020-07-30 21:41 ` Mathieu Poirier
2020-07-31 9:51 ` Suzuki K Poulose
2020-07-31 9:51 ` Suzuki K Poulose
2020-07-22 17:20 ` [RFC PATCH 10/14] coresight: etm4x: Define DEVARCH register fields Suzuki K Poulose
2020-07-22 17:20 ` Suzuki K Poulose
2020-07-22 17:20 ` [RFC PATCH 11/14] coresight: etm4x: Detect system register access support Suzuki K Poulose
2020-07-22 17:20 ` Suzuki K Poulose
2020-07-22 17:20 ` [RFC PATCH 12/14] coresight: etm4x: Refactor probing routine Suzuki K Poulose
2020-07-22 17:20 ` Suzuki K Poulose
2020-07-22 17:20 ` [RFC PATCH 13/14] coresight: etm4x: Add support for sysreg only devices Suzuki K Poulose
2020-07-22 17:20 ` Suzuki K Poulose
2020-07-22 17:20 ` [RFC PATCH 14/14] dts: bindings: coresight: ETMv4.4 system register access only units Suzuki K Poulose
2020-07-22 17:20 ` Suzuki K Poulose
2020-07-23 17:27 ` Rob Herring
2020-07-23 17:27 ` Rob Herring
2020-07-29 17:20 ` Mathieu Poirier
2020-07-29 17:20 ` Mathieu Poirier
2020-07-30 16:38 ` Suzuki K Poulose
2020-07-30 16:38 ` Suzuki K Poulose
2020-08-10 20:14 ` Mathieu Poirier
2020-08-10 20:14 ` Mathieu Poirier
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=202007300427.kO0zle7x%lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.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 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.