From: Vinod Koul <vkoul@kernel.org>
To: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
Cc: Mark Brown <broonie@kernel.org>,
Kishon Vijay Abraham I <kishon@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 after merge of the phy-next tree
Date: Tue, 15 Sep 2026 13:31:43 +0530 [thread overview]
Message-ID: <aqj7Z__J2CqeBISU@parshuram> (raw)
In-Reply-To: <351ce005-b7d9-4333-adce-896248c2d7dc@collabora.com>
On 15-09-26, 09:40, AngeloGioacchino Del Regno wrote:
> On 9/14/26 16:51, Mark Brown wrote:
> > Hi all,
> >
> > After merging the phy-next tree, today's linux-next build (x86_64
> > allmodconfig) failed like this:
>
> There's a fix already:
>
> https://lore.kernel.org/all/20260913172930.1150324-1-sashal@kernel.org/
picked thanks. somehow my builder also missed this.
--
~Vinod
next prev parent reply other threads:[~2026-09-15 8:01 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-14 14:51 Mark Brown
2026-09-15 7:40 ` AngeloGioacchino Del Regno
2026-09-15 8:01 ` Vinod Koul [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-08-18 5:40 Stephen Rothwell
2023-08-22 14:00 ` Vinod Koul
2023-02-13 2:55 Stephen Rothwell
2023-02-13 5:17 ` Vinod Koul
2022-07-07 5:39 Stephen Rothwell
2022-07-07 5:53 ` Vinod Koul
2021-12-24 3:03 Stephen Rothwell
2021-12-24 4:37 ` Vinod Koul
2021-12-15 13:49 broonie
2021-12-15 14:14 ` Marcel Ziswiler
2021-12-15 15:20 ` Vinod Koul
2020-12-01 6:07 Stephen Rothwell
2020-12-01 6:45 ` Sergio Paracuellos
2020-12-01 10:39 ` Vinod Koul
2020-11-17 2:40 Stephen Rothwell
2020-11-17 10:00 ` Vinod Koul
2020-11-18 2:56 ` Stephen Rothwell
2020-11-18 4:23 ` Vinod Koul
2019-08-27 5:50 Stephen Rothwell
2017-03-30 3:47 Stephen Rothwell
2017-03-30 5:39 ` Kishon Vijay Abraham I
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=aqj7Z__J2CqeBISU@parshuram \
--to=vkoul@kernel.org \
--cc=angelogioacchino.delregno@collabora.com \
--cc=broonie@kernel.org \
--cc=kishon@kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®