From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Christoph Hellwig <hch@lst.de>
Cc: Alexander Lobakin <aleksander.lobakin@intel.com>,
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 dma-mapping tree
Date: Wed, 8 May 2024 09:16:31 +1000 [thread overview]
Message-ID: <20240508091631.1ec34a25@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 1038 bytes --]
Hi all,
After merging the dma-mapping tree, today's linux-next build (x86_64
allmodconfig) failed like this:
net/core/page_pool.c: In function '__page_pool_dma_sync_for_device':
net/core/page_pool.c:406:54: error: passing argument 1 of 'page_pool_get_dma_addr' discards 'const' qualifier from pointer target type [-Werror=discarded-qualifiers]
406 | dma_addr_t dma_addr = page_pool_get_dma_addr(page);
| ^~~~
In file included from net/core/page_pool.c:13:
include/net/page_pool/helpers.h:373:62: note: expected 'struct page *' but argument is of type 'const struct page *'
373 | static inline dma_addr_t page_pool_get_dma_addr(struct page *page)
| ~~~~~~~~~~~~~^~~~
cc1: all warnings being treated as errors
Caused by commit
8bf4d7154d4c ("page_pool: check for DMA sync shortcut earlier")
I have used the dma-mapping tree from next-20240507 for today.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2024-05-07 23:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-07 23:16 Stephen Rothwell [this message]
2024-05-08 6:51 ` linux-next: build failure after merge of the dma-mapping tree Christoph Hellwig
2024-05-08 8:51 ` Alexander Lobakin
2024-05-08 13:45 ` Christoph Hellwig
-- strict thread matches above, loose matches on Subject: below --
2020-11-27 6:58 Stephen Rothwell
2020-11-27 9:21 ` Christoph Hellwig
2020-11-27 9:59 ` Stephen Rothwell
2020-11-27 9:33 ` Christoph Hellwig
2012-02-13 5:40 Stephen Rothwell
2012-02-13 7:31 ` Kyungmin Park
2012-02-13 15:05 ` Marek Szyprowski
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=20240508091631.1ec34a25@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=aleksander.lobakin@intel.com \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).