From: Alexandre Belloni <alexandre.belloni@bootlin.com>
To: Mark Brown <broonie@kernel.org>
Cc: Boris Brezillon <boris.brezillon@collabora.com>,
Jorge Marques <jorge.marques@analog.com>,
Frank Li <Frank.Li@nxp.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 i3c tree
Date: Wed, 17 Sep 2025 19:35:41 +0200 [thread overview]
Message-ID: <20250917173541a0e86f6e@mail.local> (raw)
In-Reply-To: <2025091619124436ec80e5@mail.local>
On 16/09/2025 21:13:03+0200, Alexandre Belloni wrote:
> Hello Mark,
>
> On 15/09/2025 21:58:12+0100, Mark Brown wrote:
> > Hi all,
> >
> > After merging the i3c tree, today's linux-next build (x86 allmodconfig)
> > failed like this:
> >
> > /tmp/next/build/drivers/i3c/master/adi-i3c-master.c:13:10: fatal error: linux/fpga/adi-axi-common.h: No such file or directory
> > 13 | #include <linux/fpga/adi-axi-common.h>
> > | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> > compilation terminated.
> >
> > Caused by commit
> >
> > 63cae74bea7cc ("i3c: master: Add driver for Analog Devices I3C Controller IP")
> >
> > I have used the version from next-20250912 instead.
>
> Thanks for the heads up, I didn't realize I wasn't rebased on top of
> v6.17-rc1. I sent a patch but I will only be able to push it tomorrow so
> the i3c tree is going to fail again today.
This should be fixed now.
--
Alexandre Belloni, co-owner and COO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2025-09-17 17:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-15 20:58 linux-next: build failure after merge of the i3c tree Mark Brown
2025-09-16 19:12 ` Alexandre Belloni
2025-09-17 17:35 ` Alexandre Belloni [this message]
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=20250917173541a0e86f6e@mail.local \
--to=alexandre.belloni@bootlin.com \
--cc=Frank.Li@nxp.com \
--cc=boris.brezillon@collabora.com \
--cc=broonie@kernel.org \
--cc=jorge.marques@analog.com \
--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 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.