From: kernel test robot <lkp@intel.com>
To: Guo Mengqi <guomengqi3@huawei.com>,
vkoul@kernel.org, dmaengine@vger.kernel.org, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, conor+dt@kernel.org,
devicetree@vger.kernel.org
Cc: oe-kbuild-all@lists.linux.dev, xuqiang36@huawei.com,
chenweilong@huawei.com, guomengqi3@huawei.com
Subject: Re: [PATCH v5 1/2] dmaengine: Add HiSilicon Ascend SDMA engine support
Date: Wed, 25 Oct 2023 02:43:27 +0800 [thread overview]
Message-ID: <202310250208.jwwNXco0-lkp@intel.com> (raw)
In-Reply-To: <20231021093454.39822-2-guomengqi3@huawei.com>
Hi Guo,
kernel test robot noticed the following build warnings:
[auto build test WARNING on vkoul-dmaengine/next]
[also build test WARNING on linus/master v6.6-rc7 next-20231024]
[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/Guo-Mengqi/dmaengine-Add-HiSilicon-Ascend-SDMA-engine-support/20231021-174034
base: https://git.kernel.org/pub/scm/linux/kernel/git/vkoul/dmaengine.git next
patch link: https://lore.kernel.org/r/20231021093454.39822-2-guomengqi3%40huawei.com
patch subject: [PATCH v5 1/2] dmaengine: Add HiSilicon Ascend SDMA engine support
config: openrisc-allyesconfig (https://download.01.org/0day-ci/archive/20231025/202310250208.jwwNXco0-lkp@intel.com/config)
compiler: or1k-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231025/202310250208.jwwNXco0-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/202310250208.jwwNXco0-lkp@intel.com/
All warnings (new ones prefixed by >>):
In file included from arch/openrisc/include/asm/mmu_context.h:18,
from include/linux/mmu_context.h:5,
from drivers/iommu/iommu-sva.c:5:
>> include/asm-generic/mm_hooks.h:10:40: warning: 'struct mm_struct' declared inside parameter list will not be visible outside of this definition or declaration
10 | static inline int arch_dup_mmap(struct mm_struct *oldmm,
| ^~~~~~~~~
include/asm-generic/mm_hooks.h:16:42: warning: 'struct mm_struct' declared inside parameter list will not be visible outside of this definition or declaration
16 | static inline void arch_exit_mmap(struct mm_struct *mm)
| ^~~~~~~~~
include/asm-generic/mm_hooks.h:20:38: warning: 'struct mm_struct' declared inside parameter list will not be visible outside of this definition or declaration
20 | static inline void arch_unmap(struct mm_struct *mm,
| ^~~~~~~~~
include/asm-generic/mm_hooks.h:25:15: error: unknown type name 'bool'
25 | static inline bool arch_vma_access_permitted(struct vm_area_struct *vma,
| ^~~~
include/asm-generic/mm_hooks.h:26:17: error: unknown type name 'bool'
26 | bool write, bool execute, bool foreign)
| ^~~~
include/asm-generic/mm_hooks.h:1:1: note: 'bool' is defined in header '<stdbool.h>'; did you forget to '#include <stdbool.h>'?
+++ |+#include <stdbool.h>
1 | /* SPDX-License-Identifier: GPL-2.0 */
include/asm-generic/mm_hooks.h:26:29: error: unknown type name 'bool'
26 | bool write, bool execute, bool foreign)
| ^~~~
include/asm-generic/mm_hooks.h:26:29: note: 'bool' is defined in header '<stdbool.h>'; did you forget to '#include <stdbool.h>'?
include/asm-generic/mm_hooks.h:26:43: error: unknown type name 'bool'
26 | bool write, bool execute, bool foreign)
| ^~~~
include/asm-generic/mm_hooks.h:26:43: note: 'bool' is defined in header '<stdbool.h>'; did you forget to '#include <stdbool.h>'?
>> arch/openrisc/include/asm/mmu_context.h:21:61: warning: 'struct mm_struct' declared inside parameter list will not be visible outside of this definition or declaration
21 | extern int init_new_context(struct task_struct *tsk, struct mm_struct *mm);
| ^~~~~~~~~
>> arch/openrisc/include/asm/mmu_context.h:21:36: warning: 'struct task_struct' declared inside parameter list will not be visible outside of this definition or declaration
21 | extern int init_new_context(struct task_struct *tsk, struct mm_struct *mm);
| ^~~~~~~~~~~
arch/openrisc/include/asm/mmu_context.h:23:36: warning: 'struct mm_struct' declared inside parameter list will not be visible outside of this definition or declaration
23 | extern void destroy_context(struct mm_struct *mm);
| ^~~~~~~~~
arch/openrisc/include/asm/mmu_context.h:25:30: warning: 'struct task_struct' declared inside parameter list will not be visible outside of this definition or declaration
25 | struct task_struct *tsk);
| ^~~~~~~~~~~
arch/openrisc/include/asm/mmu_context.h:24:30: warning: 'struct mm_struct' declared inside parameter list will not be visible outside of this definition or declaration
24 | extern void switch_mm(struct mm_struct *prev, struct mm_struct *next,
| ^~~~~~~~~
arch/openrisc/include/asm/mmu_context.h:33:17: error: unknown type name 'pgd_t'
33 | extern volatile pgd_t *current_pgd[]; /* defined in arch/openrisc/mm/fault.c */
| ^~~~~
include/linux/mmu_context.h:39:15: error: unknown type name 'bool'
39 | static inline bool arch_pgtable_dma_compat(struct mm_struct *mm)
| ^~~~
include/linux/mmu_context.h: In function 'arch_pgtable_dma_compat':
include/linux/mmu_context.h:41:16: error: 'true' undeclared (first use in this function)
41 | return true;
| ^~~~
include/linux/mmu_context.h:7:1: note: 'true' is defined in header '<stdbool.h>'; did you forget to '#include <stdbool.h>'?
6 | #include <asm/mmu.h>
+++ |+#include <stdbool.h>
7 |
include/linux/mmu_context.h:41:16: note: each undeclared identifier is reported only once for each function it appears in
41 | return true;
| ^~~~
include/linux/mmu_context.h:42:1: error: control reaches end of non-void function [-Werror=return-type]
42 | }
| ^
cc1: some warnings being treated as errors
vim +10 include/asm-generic/mm_hooks.h
d6dd61c831226f Jeremy Fitzhardinge 2007-05-02 9
c10e83f598d080 Thomas Gleixner 2017-12-14 @10 static inline int arch_dup_mmap(struct mm_struct *oldmm,
d6dd61c831226f Jeremy Fitzhardinge 2007-05-02 11 struct mm_struct *mm)
d6dd61c831226f Jeremy Fitzhardinge 2007-05-02 12 {
c10e83f598d080 Thomas Gleixner 2017-12-14 13 return 0;
d6dd61c831226f Jeremy Fitzhardinge 2007-05-02 14 }
d6dd61c831226f Jeremy Fitzhardinge 2007-05-02 15
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2023-10-24 18:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-21 9:34 [PATCH v5 0/2] Add dma controller driver for HiSilicon Ascend310/910 Guo Mengqi
2023-10-21 9:34 ` [PATCH v5 1/2] dmaengine: Add HiSilicon Ascend SDMA engine support Guo Mengqi
2023-10-24 18:43 ` kernel test robot [this message]
2023-10-24 20:10 ` kernel test robot
2023-10-21 9:34 ` [PATCH v5 2/2] dt-bindings: dma: HiSilicon: Add bindings for HiSilicon Ascend sdma Guo Mengqi
2023-10-21 10:18 ` Rob Herring
2023-10-24 2:04 ` guomengqi (A)
2023-10-22 21:13 ` Rob Herring
2023-10-23 9:08 ` guomengqi (A)
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=202310250208.jwwNXco0-lkp@intel.com \
--to=lkp@intel.com \
--cc=chenweilong@huawei.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=guomengqi3@huawei.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=robh+dt@kernel.org \
--cc=vkoul@kernel.org \
--cc=xuqiang36@huawei.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.