From: kbuild test robot <lkp@intel.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: kbuild-all@01.org, linux-gpio@vger.kernel.org,
Thierry Reding <treding@nvidia.com>,
Brian Masney <masneyb@onstation.org>
Subject: [gpio:devel 21/25] drivers/gpio/gpiolib.c:2112:28: error: 'struct gpio_irq_chip' has no member named 'child_offset_to_irq'
Date: Wed, 14 Aug 2019 20:23:09 +0800 [thread overview]
Message-ID: <201908142007.V8WIQ09z%lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2617 bytes --]
tree: https://kernel.googlesource.com/pub/scm/linux/kernel/git/linusw/linux-gpio.git devel
head: 470219c619e9f76e41497b9a90f2ec61dbedf3f2
commit: 9d5f07204350d557ec1e2d9bd2f779b45b490931 [21/25] gpio: Add support for hierarchical IRQ domains
config: nios2-10m50_defconfig (attached as .config)
compiler: nios2-linux-gcc (GCC) 7.4.0
reproduce:
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
git checkout 9d5f07204350d557ec1e2d9bd2f779b45b490931
# save the attached .config to linux build tree
GCC_VERSION=7.4.0 make.cross ARCH=nios2
If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
drivers/gpio/gpiolib.c: In function 'gpiochip_to_irq':
>> drivers/gpio/gpiolib.c:2112:28: error: 'struct gpio_irq_chip' has no member named 'child_offset_to_irq'
spec.param[0] = chip->irq.child_offset_to_irq(chip, offset);
^
In file included from include/asm-generic/gpio.h:13:0,
from include/linux/gpio.h:62,
from drivers/gpio/gpiolib.c:13:
At top level:
include/linux/gpio/driver.h:553:13: warning: 'gpiochip_populate_parent_fwspec_fourcell' defined but not used [-Wunused-function]
static void gpiochip_populate_parent_fwspec_fourcell(struct gpio_chip *chip,
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
include/linux/gpio/driver.h:546:13: warning: 'gpiochip_populate_parent_fwspec_twocell' defined but not used [-Wunused-function]
static void gpiochip_populate_parent_fwspec_twocell(struct gpio_chip *chip,
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
vim +2112 drivers/gpio/gpiolib.c
2099
2100 static int gpiochip_to_irq(struct gpio_chip *chip, unsigned offset)
2101 {
2102 struct irq_domain *domain = chip->irq.domain;
2103
2104 if (!gpiochip_irqchip_irq_valid(chip, offset))
2105 return -ENXIO;
2106
2107 if (irq_domain_is_hierarchy(domain)) {
2108 struct irq_fwspec spec;
2109
2110 spec.fwnode = domain->fwnode;
2111 spec.param_count = 2;
> 2112 spec.param[0] = chip->irq.child_offset_to_irq(chip, offset);
2113 spec.param[1] = IRQ_TYPE_NONE;
2114
2115 return irq_create_fwspec_mapping(&spec);
2116 }
2117
2118 return irq_create_mapping(domain, offset);
2119 }
2120
---
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: 9849 bytes --]
reply other threads:[~2019-08-14 12:23 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=201908142007.V8WIQ09z%lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@01.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=masneyb@onstation.org \
--cc=treding@nvidia.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;
as well as URLs for NNTP newsgroup(s).