From: kernel test robot <lkp@intel.com>
To: Jia Wang via B4 Relay <devnull+wangjia.ultrarisc.com@kernel.org>,
Hoan Tran <hoan@os.amperecomputing.com>,
Linus Walleij <linusw@kernel.org>,
Bartosz Golaszewski <brgl@kernel.org>
Cc: oe-kbuild-all@lists.linux.dev, linux-gpio@vger.kernel.org,
linux-kernel@vger.kernel.org, Jia Wang <wangjia@ultrarisc.com>
Subject: Re: [PATCH] gpio: dwapb: Defer clock gating until noirq
Date: Mon, 29 Jun 2026 18:04:47 +0800 [thread overview]
Message-ID: <202606291736.mAgOeA65-lkp@intel.com> (raw)
In-Reply-To: <20260629-gpio-dwapb-wakeup-v1-1-3394f02317da@ultrarisc.com>
Hi Jia,
kernel test robot noticed the following build errors:
[auto build test ERROR on dc59e4fea9d83f03bad6bddf3fa2e52491777482]
url: https://github.com/intel-lab-lkp/linux/commits/Jia-Wang-via-B4-Relay/gpio-dwapb-Defer-clock-gating-until-noirq/20260629-135404
base: dc59e4fea9d83f03bad6bddf3fa2e52491777482
patch link: https://lore.kernel.org/r/20260629-gpio-dwapb-wakeup-v1-1-3394f02317da%40ultrarisc.com
patch subject: [PATCH] gpio: dwapb: Defer clock gating until noirq
config: sparc64-randconfig-001-20260629 (https://download.01.org/0day-ci/archive/20260629/202606291736.mAgOeA65-lkp@intel.com/config)
compiler: sparc64-linux-gcc (GCC) 8.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260629/202606291736.mAgOeA65-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/202606291736.mAgOeA65-lkp@intel.com/
All errors (new ones prefixed by >>):
drivers/gpio/gpio-dwapb.c: In function 'dwapb_irq_set_wake':
>> drivers/gpio/gpio-dwapb.c:377:7: error: 'struct irq_data' has no member named 'parent_data'
if (d->parent_data && !!ctx->wake_en != !!wake_en) {
^~
>> drivers/gpio/gpio-dwapb.c:378:9: error: implicit declaration of function 'irq_chip_set_wake_parent'; did you mean 'irq_set_parent'? [-Werror=implicit-function-declaration]
err = irq_chip_set_wake_parent(d, enable);
^~~~~~~~~~~~~~~~~~~~~~~~
irq_set_parent
cc1: some warnings being treated as errors
vim +377 drivers/gpio/gpio-dwapb.c
362
363 static int dwapb_irq_set_wake(struct irq_data *d, unsigned int enable)
364 {
365 struct gpio_chip *gc = irq_data_get_irq_chip_data(d);
366 struct dwapb_gpio *gpio = to_dwapb_gpio(gc);
367 struct dwapb_context *ctx = gpio->ports[0].ctx;
368 irq_hw_number_t bit = irqd_to_hwirq(d);
369 u32 wake_en = ctx->wake_en;
370 int err;
371
372 if (enable)
373 wake_en |= BIT(bit);
374 else
375 wake_en &= ~BIT(bit);
376
> 377 if (d->parent_data && !!ctx->wake_en != !!wake_en) {
> 378 err = irq_chip_set_wake_parent(d, enable);
379 if (err)
380 return err;
381 }
382
383 ctx->wake_en = wake_en;
384
385 return 0;
386 }
387
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2026-06-29 10:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-29 5:30 [PATCH] gpio: dwapb: Defer clock gating until noirq Jia Wang via B4 Relay
2026-06-29 10:04 ` kernel test robot [this message]
2026-07-02 6:26 ` Jia Wang
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=202606291736.mAgOeA65-lkp@intel.com \
--to=lkp@intel.com \
--cc=brgl@kernel.org \
--cc=devnull+wangjia.ultrarisc.com@kernel.org \
--cc=hoan@os.amperecomputing.com \
--cc=linusw@kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=wangjia@ultrarisc.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