From: Mark Brown <broonie@kernel.org>
To: Matthew Wilcox <willy@infradead.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: build failure after merge of the pagemap-headers tree
Date: Tue, 25 Aug 2026 14:35:17 +0100 [thread overview]
Message-ID: <ao2aFX-4nXH8x-7Y@sirena.org.uk> (raw)
[-- Attachment #1: Type: text/plain, Size: 2973 bytes --]
Hi all,
After merging the pagemap-headers tree, today's linux-next build
(arm multi_v7_defconfig) failed like this:
/tmp/next/build/drivers/dma/ste_dma40.c:492:42: error: field 'tasklet' has incomplete type
492 | struct tasklet_struct tasklet;
| ^~~~~~~
/tmp/next/build/drivers/dma/ste_dma40.c: In function 'dma_tc_handle':
/tmp/next/build/drivers/dma/ste_dma40.c:1590:9: error: implicit declaration of function 'tasklet_schedule' [-Wimplicit-function-declaration]
1590 | tasklet_schedule(&d40c->tasklet);
| ^~~~~~~~~~~~~~~~
/tmp/next/build/drivers/dma/ste_dma40.c: In function 'dma_tasklet':
/tmp/next/build/drivers/dma/ste_dma40.c:1596:33: error: implicit declaration of function 'from_tasklet'; did you mean 'dma_tasklet'? [-Wimplicit-function-declaration]
1596 | struct d40_chan *d40c = from_tasklet(d40c, t, tasklet);
| ^~~~~~~~~~~~
| dma_tasklet
/tmp/next/build/drivers/dma/ste_dma40.c:1596:55: error: 'tasklet' undeclared (first use in this function)
1596 | struct d40_chan *d40c = from_tasklet(d40c, t, tasklet);
| ^~~~~~~
/tmp/next/build/drivers/dma/ste_dma40.c:1596:55: note: each undeclared identifier is reported only once for each function it appears in
/tmp/next/build/drivers/dma/ste_dma40.c: At top level:
/tmp/next/build/drivers/dma/ste_dma40.c:1659:8: error: unknown type name 'irqreturn_t'
1659 | static irqreturn_t d40_handle_interrupt(int irq, void *data)
| ^~~~~~~~~~~
/tmp/next/build/drivers/dma/ste_dma40.c: In function 'd40_handle_interrupt':
/tmp/next/build/drivers/dma/ste_dma40.c:1718:16: error: 'IRQ_HANDLED' undeclared (first use in this function)
1718 | return IRQ_HANDLED;
| ^~~~~~~~~~~
/tmp/next/build/drivers/dma/ste_dma40.c: In function 'd40_chan_init':
/tmp/next/build/drivers/dma/ste_dma40.c:2818:17: error: implicit declaration of function 'tasklet_setup'; did you mean 'timer_setup'? [-Wimplicit-function-declaration]
2818 | tasklet_setup(&d40c->tasklet, dma_tasklet);
| ^~~~~~~~~~~~~
| timer_setup
/tmp/next/build/drivers/dma/ste_dma40.c: In function 'd40_probe':
/tmp/next/build/drivers/dma/ste_dma40.c:3588:15: error: implicit declaration of function 'request_irq'; did you mean 'request_key'? [-Wimplicit-function-declaration]
3588 | ret = request_irq(base->irq, d40_handle_interrupt, 0, D40_NAME, base);
| ^~~~~~~~~~~
| request_key
/tmp/next/build/drivers/dma/ste_dma40.c: In function 'd40_handle_interrupt':
/tmp/next/build/drivers/dma/ste_dma40.c:1719:1: error: control reaches end of non-void function [-Werror=return-type]
1719 | }
| ^
Doubtless caused by the pagemap-headers tree. I will not merge the tree
today.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
reply other threads:[~2026-08-25 13:35 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=ao2aFX-4nXH8x-7Y@sirena.org.uk \
--to=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=willy@infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox