From: kbuild test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [android-common:android-mainline 10/10] include/linux/soc/qcom/irq.h:27:15: error: unknown type name 'bool'
Date: Sun, 27 Oct 2019 04:41:36 +0800 [thread overview]
Message-ID: <201910270434.2QkYyrpA%lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3960 bytes --]
tree: https://android.googlesource.com/kernel/common android-mainline
head: a59c2b66751530d33cfe5273dc5ceddb98f8ddb9
commit: a59c2b66751530d33cfe5273dc5ceddb98f8ddb9 [10/10] FROMLIST: drivers: pinctrl: msm: setup GPIO chip in hierarchy
config: x86_64-allyesconfig (attached as .config)
compiler: gcc-7 (Debian 7.4.0-14) 7.4.0
reproduce:
git checkout a59c2b66751530d33cfe5273dc5ceddb98f8ddb9
# save the attached .config to linux build tree
make ARCH=x86_64
If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>
Note: the android-common/android-mainline HEAD f8978f4f6a5ed1babb76f7f98c98050a73c666bc builds fine.
It only hurts bisectibility.
All error/warnings (new ones prefixed by >>):
In file included from <command-line>:0:0:
>> include/linux/soc/qcom/irq.h:27:15: error: unknown type name 'bool'
static inline bool irq_domain_qcom_handle_wakeup(struct irq_domain *parent)
^~~~
>> include/linux/soc/qcom/irq.h:27:57: warning: 'struct irq_domain' declared inside parameter list will not be visible outside of this definition or declaration
static inline bool irq_domain_qcom_handle_wakeup(struct irq_domain *parent)
^~~~~~~~~~
include/linux/soc/qcom/irq.h: In function 'irq_domain_qcom_handle_wakeup':
>> include/linux/soc/qcom/irq.h:29:16: error: dereferencing pointer to incomplete type 'struct irq_domain'
return (parent->flags & IRQ_DOMAIN_FLAG_QCOM_PDC_WAKEUP);
^~
>> include/linux/soc/qcom/irq.h:16:43: error: 'IRQ_DOMAIN_FLAG_NONCORE' undeclared (first use in this function); did you mean 'IRQ_DOMAIN_FLAG_QCOM_PDC_WAKEUP'?
#define IRQ_DOMAIN_FLAG_QCOM_PDC_WAKEUP (IRQ_DOMAIN_FLAG_NONCORE << 0)
^
>> include/linux/soc/qcom/irq.h:29:26: note: in expansion of macro 'IRQ_DOMAIN_FLAG_QCOM_PDC_WAKEUP'
return (parent->flags & IRQ_DOMAIN_FLAG_QCOM_PDC_WAKEUP);
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
include/linux/soc/qcom/irq.h:16:43: note: each undeclared identifier is reported only once for each function it appears in
#define IRQ_DOMAIN_FLAG_QCOM_PDC_WAKEUP (IRQ_DOMAIN_FLAG_NONCORE << 0)
^
>> include/linux/soc/qcom/irq.h:29:26: note: in expansion of macro 'IRQ_DOMAIN_FLAG_QCOM_PDC_WAKEUP'
return (parent->flags & IRQ_DOMAIN_FLAG_QCOM_PDC_WAKEUP);
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
vim +/bool +27 include/linux/soc/qcom/irq.h
7
8 /**
9 * QCOM specific IRQ domain flags that distinguishes the handling of wakeup
10 * capable interrupts by different interrupt controllers.
11 *
12 * IRQ_DOMAIN_FLAG_QCOM_PDC_WAKEUP: Line must be masked at TLMM and the
13 * interrupt configuration is done at PDC
14 * IRQ_DOMAIN_FLAG_QCOM_MPM_WAKEUP: Interrupt configuration is handled at TLMM
15 */
> 16 #define IRQ_DOMAIN_FLAG_QCOM_PDC_WAKEUP (IRQ_DOMAIN_FLAG_NONCORE << 0)
17 #define IRQ_DOMAIN_FLAG_QCOM_MPM_WAKEUP (IRQ_DOMAIN_FLAG_NONCORE << 1)
18
19 /**
20 * irq_domain_qcom_handle_wakeup: Return if the domain handles interrupt
21 * configuration
22 * @parent: irq domain
23 *
24 * This QCOM specific irq domain call returns if the interrupt controller
25 * requires the interrupt be masked@the child interrupt controller.
26 */
> 27 static inline bool irq_domain_qcom_handle_wakeup(struct irq_domain *parent)
28 {
> 29 return (parent->flags & IRQ_DOMAIN_FLAG_QCOM_PDC_WAKEUP);
30 }
31
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 70298 bytes --]
reply other threads:[~2019-10-26 20:41 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=201910270434.2QkYyrpA%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.