public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Maxime Ripard <mripard@kernel.org>,
	Albert Esteve <aesteve@redhat.com>,
	"T.J. Mercier" <tjmercier@google.com>,
	Marek Szyprowski <m.szyprowski@samsung.com>
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 dma-mapping tree
Date: Fri, 27 Mar 2026 20:07:04 +0000	[thread overview]
Message-ID: <acbjaDJ1a-YQC64d@sirena.co.uk> (raw)

[-- Attachment #1: Type: text/plain, Size: 399 bytes --]

Hi all,

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.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

             reply	other threads:[~2026-03-27 20:07 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 [this message]
2026-03-30  7:56   ` linux-next: build failure after merge of the dma-mapping tree Marek Szyprowski
2026-03-30  8:11     ` Maxime Ripard
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=acbjaDJ1a-YQC64d@sirena.co.uk \
    --to=broonie@kernel.org \
    --cc=aesteve@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=m.szyprowski@samsung.com \
    --cc=mripard@kernel.org \
    --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