From: Maxime Ripard <mripard@kernel.org>
To: Marek Szyprowski <m.szyprowski@samsung.com>
Cc: Mark Brown <broonie@kernel.org>,
Albert Esteve <aesteve@redhat.com>,
"T.J. Mercier" <tjmercier@google.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: build failure after merge of the dma-mapping tree
Date: Mon, 30 Mar 2026 10:11:23 +0200 [thread overview]
Message-ID: <20260330-petite-gifted-wildebeest-ff150a@houat> (raw)
In-Reply-To: <9f63a789-79b6-46fe-8177-b08e1ec120f9@samsung.com>
[-- Attachment #1: Type: text/plain, Size: 890 bytes --]
Hi Mark, Marek,
On Mon, Mar 30, 2026 at 09:56:30AM +0200, Marek Szyprowski wrote:
> On 27.03.2026 21:07, Mark Brown wrote:
> > After merging the dma-mapping tree, today's linux-next build (x86_64
> > allmodconfig) failed like this:
> >
> > x86_64-linux-gnu-ld: vmlinux.o: in function `dma_contiguous_reserve':
> > (.init.text+0xbf3bb): undefined reference to `dma_heap_cma_register_heap'
> >
> > Caused by commit
> >
> > 3a236f6a5cf2da (dma: contiguous: Turn heap registration logic around)
> >
> > I have used the version from next-20260326 instead.
>
> Thanks for the information. I've dropped that commit from dma-mapping-for-next.
I'm not sure how it ended up that way, but I have a fix queued up. It
should just remove a bunch of loose ends that were left with the
original patch.
I'm waiting for allmodconfig to finish and I'll send it.
Sorry,
Maxime
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 273 bytes --]
next prev parent reply other threads:[~2026-03-30 8:11 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20260327200715eucas1p1953ce4c0b4d4e0cd95844f0acdb7ac3a@eucas1p1.samsung.com>
2026-03-27 20:07 ` Mark Brown
2026-03-30 7:56 ` Marek Szyprowski
2026-03-30 8:11 ` Maxime Ripard [this message]
2024-07-10 1:05 Stephen Rothwell
2024-07-10 5:58 ` Christoph Hellwig
-- strict thread matches above, loose matches on Subject: below --
2024-05-07 23:16 Stephen Rothwell
2024-05-08 6:51 ` Christoph Hellwig
2024-05-08 8:51 ` Alexander Lobakin
2024-05-08 13:45 ` Christoph Hellwig
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=20260330-petite-gifted-wildebeest-ff150a@houat \
--to=mripard@kernel.org \
--cc=aesteve@redhat.com \
--cc=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=tjmercier@google.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
all inboxes | Powered by JetHome®