From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Mark Brown <broonie@kernel.org>
Cc: Richard Weinberger <richard.weinberger@gmail.com>,
Bernhard Frauendienst <kernel@nospam.obeliks.de>,
Amit Kumar Mahapatra <amit.kumar-mahapatra@amd.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 mtd tree
Date: Mon, 02 Feb 2026 09:47:25 +0100 [thread overview]
Message-ID: <875x8filb6.fsf@bootlin.com> (raw)
In-Reply-To: <aXzSe9_CZr7x8Qqg@sirena.org.uk> (Mark Brown's message of "Fri, 30 Jan 2026 15:47:07 +0000")
Hi,
On 30/01/2026 at 15:47:07 GMT, Mark Brown <broonie@kernel.org> wrote:
> Hi all,
>
> After merging the mtd tree, today's linux-next build (arm64 defconfig)
> failed like this:
>
> ld: Unexpected GOT/PLT entries detected!
> ld: Unexpected run-time procedure linkages detected!
> ld: drivers/mtd/mtdcore.o: in function `cleanup_mtd':
> /tmp/next/build/drivers/mtd/mtdcore.c:2641:(.exit.text+0x18): undefined reference to `mtd_virt_concat_destroy_joins'
> ld: /tmp/next/build/drivers/mtd/mtdcore.c:2642:(.exit.text+0x1c): undefined reference to `mtd_virt_concat_destroy_items'
>
> Caused by commit
>
> 285871f1ff3c2 (mtd: Add driver for concatenating devices)
>
> I have used the version from next-20260129 instead.
Sorry for that, I believe I removed it on Thursday evening due to some
robot report, but it already reached -next.
Cheers,
Miquèl
next prev parent reply other threads:[~2026-02-02 8:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-30 15:47 linux-next: build failure after merge of the mtd tree Mark Brown
2026-02-02 8:47 ` Miquel Raynal [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-03-12 13:14 Mark Brown
2026-03-12 14:22 ` Andy Shevchenko
2025-09-02 2:08 Stephen Rothwell
2025-09-02 5:25 ` Mahapatra, Amit Kumar
2025-09-02 5:45 ` Stephen Rothwell
2021-02-15 1:28 Stephen Rothwell
2021-02-15 8:55 ` Rafał Miłecki
2010-04-08 1:42 Stephen Rothwell
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=875x8filb6.fsf@bootlin.com \
--to=miquel.raynal@bootlin.com \
--cc=amit.kumar-mahapatra@amd.com \
--cc=broonie@kernel.org \
--cc=kernel@nospam.obeliks.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=richard.weinberger@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.