From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Manuel Ebner <manuelebner@mailbox.org>
Cc: Mark Brown <broonie@kernel.org>, Johan Hovold <johan@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: build failure in the final build
Date: Fri, 17 Jul 2026 16:35:44 +0200 [thread overview]
Message-ID: <2026071734-papyrus-unmovable-5826@gregkh> (raw)
In-Reply-To: <c2fe4a81c639cddb65116d9b3526e82206927c0d.camel@mailbox.org>
On Fri, Jul 17, 2026 at 03:47:55PM +0200, Manuel Ebner wrote:
> Hi Mark,
>
> On Wed, 2026-07-15 at 16:37 +0100, Mark Brown wrote:
> > On Mon, Jul 13, 2026 at 06:48:32PM +0100, Mark Brown wrote:
> > > Hi all,
> > >
> > > In the final builds, today's linux-next build (arm64 allyesconfig)
> > > failed like this:
> >
> > This error is due to a71f5aef1be98 (USB: gadget: fsl-udc: enable compile
> > testing) from the usb tree, a dependency change as expected. I'll do
> > something about this tomorrow.
>
> I stumbled across the same build errors. Are you still on this?
Should I revert that commit to resolve this?
thanks,
greg k-h
next prev parent reply other threads:[~2026-07-17 14:35 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-13 17:48 linux-next: build failure in the final build Mark Brown
2026-07-15 15:37 ` Mark Brown
2026-07-17 13:47 ` Manuel Ebner
2026-07-17 14:35 ` Greg Kroah-Hartman [this message]
2026-07-17 14:40 ` Johan Hovold
2026-07-17 14:54 ` Mark Brown
2026-07-17 15:06 ` Johan Hovold
-- strict thread matches above, loose matches on Subject: below --
2026-07-07 12:11 linux-next: build warnings after merge of the kvm-arm-fixes tree Mark Brown
2026-07-07 12:58 ` linux-next: Build failure in the final build Mark Brown
2026-07-06 14:50 linux-next: build " Mark Brown
2026-07-06 14:52 ` Johannes Berg
2026-06-10 15:51 Mark Brown
2026-01-21 17:14 Mark Brown
2026-01-21 17:18 ` Miguel Ojeda
2026-01-21 17:24 ` Mark Brown
2026-01-21 18:14 ` Miguel Ojeda
2026-01-21 19:14 ` Alice Ryhl
2026-01-21 19:24 ` Miguel Ojeda
2026-01-22 11:20 ` Mark Brown
2026-01-22 0:42 ` Deborah Brouwer
2026-01-22 11:17 ` Mark Brown
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=2026071734-papyrus-unmovable-5826@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=broonie@kernel.org \
--cc=johan@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=manuelebner@mailbox.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox