From: Johan Hovold <johan@kernel.org>
To: Mark Brown <broonie@kernel.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Manuel Ebner <manuelebner@mailbox.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 17:06:42 +0200 [thread overview]
Message-ID: <alpFAvt1AExGKx5f@hovoldconsulting.com> (raw)
In-Reply-To: <99d6a70c-3986-4267-9934-e8d8b293cb47@sirena.org.uk>
[-- Attachment #1: Type: text/plain, Size: 872 bytes --]
On Fri, Jul 17, 2026 at 03:54:05PM +0100, Mark Brown wrote:
> On Fri, Jul 17, 2026 at 04:40:38PM +0200, Johan Hovold wrote:
>
> > I was also waiting on Mark to follow up on this, otherwise I can take
> > closer look at it.
>
> > Based on a quick look it seemed like Mark was right about missing static
> > keywords in a driver indirectly enabled by the "offending" commit.
>
> IIRC I replied to the patch for the offending commit the other day. At
> some point I will get fed up and just revert the usb tree back to one
> that works, it's a real pain doing that for issues in the final build.
>
> This seems like it really ought to be straightforward to reproduce
> localy...
Oh, sorry. I misunderstood your comment about doing "something about
this tomorrow" to mean that you intended to send a fix yourself.
I'll send a fix in a bit.
Johan
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 265 bytes --]
next prev parent reply other threads:[~2026-07-17 15:06 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
2026-07-17 14:40 ` Johan Hovold
2026-07-17 14:54 ` Mark Brown
2026-07-17 15:06 ` Johan Hovold [this message]
-- 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=alpFAvt1AExGKx5f@hovoldconsulting.com \
--to=johan@kernel.org \
--cc=broonie@kernel.org \
--cc=gregkh@linuxfoundation.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 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.