From: Andy Shevchenko <andriy.shevchenko@linux•intel.com>
To: Mark Brown <broonie@kernel•org>
Cc: Richard Weinberger <richard.weinberger@gmail•com>,
Randy Dunlap <rdunlap@infradead•org>,
Miquel Raynal <miquel.raynal@bootlin•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: Thu, 12 Mar 2026 16:22:07 +0200 [thread overview]
Message-ID: <abLMD1d5ft4xyFgH@ashevche-desk.local> (raw)
In-Reply-To: <abK8KXC70RC2K_fW@sirena.org.uk>
On Thu, Mar 12, 2026 at 01:14:17PM +0000, Mark Brown wrote:
> Hi all,
>
> After merging the mtd tree, today's linux-next build (KCONFIG_NAME)
> failed like this:
>
> /tmp/next/build/drivers/mtd/maps/physmap-core.c: In function 'physmap_flash_of_init':
> /tmp/next/build/drivers/mtd/maps/physmap-core.c:367:23: error: implicit declaration of function 'of_flash_probe_bt1_rom'; did you mean 'of_flash_probe_ixp4xx'? [-Wimplicit-function-declaration]
> 367 | err = of_flash_probe_bt1_rom(dev, dp, &info->maps[i]);
> | ^~~~~~~~~~~~~~~~~~~~~~
> | of_flash_probe_ixp4xx
>
> Caused by commit
>
> 16d68d10f5b93 (mtd: physmap: physmap-bt1-rom: Remove not-going-to-be-supported code for Baikal SoC)
>
> I have used the version from 20260311 instead.
Yeah, sorry for that, I will send a follow up that may be applied on top or
squashed with the original change.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2026-03-12 14:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-12 13:14 linux-next: build failure after merge of the mtd tree Mark Brown
2026-03-12 14:22 ` Andy Shevchenko [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-01-30 15:47 Mark Brown
2026-02-02 8:47 ` Miquel Raynal
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=abLMD1d5ft4xyFgH@ashevche-desk.local \
--to=andriy.shevchenko@linux$(echo .)intel.com \
--cc=broonie@kernel$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=miquel.raynal@bootlin$(echo .)com \
--cc=rdunlap@infradead$(echo .)org \
--cc=richard.weinberger@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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