From: Steven Rostedt <rostedt@goodmis.org>
To: Mykyta Yatsenko <yatsenko@meta.com>
Cc: Mark Brown <broonie@kernel.org>,
mhiramat@kernel.org, mathieu.desnoyers@efficios.com,
"mykyta.yatsenko5@gmail.com" <mykyta.yatsenko5@gmail.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 in final build
Date: Wed, 5 Aug 2026 16:23:27 -0400 [thread overview]
Message-ID: <20260805162327.4dee0a76@gandalf.local.home> (raw)
In-Reply-To: <CAFsYEOKG7=Os-jLadKF2pcfb9Thh20e9HhOvU288fhkBHziLGw@mail.gmail.com>
On Tue, 4 Aug 2026 12:48:37 +0100
Mykyta Yatsenko <yatsenko@meta.com> wrote:
> It looks like Steven is on vacation, I'm adding Masami and Mathieu to
> the thread.
I'm back. I'll start testing it today.
-- Steve
next prev parent reply other threads:[~2026-08-05 20:22 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-29 15:34 linux-next: build failure in final build Mark Brown
2026-07-30 9:14 ` Mykyta Yatsenko
2026-08-03 16:35 ` Mark Brown
2026-08-04 11:35 ` Mykyta Yatsenko
2026-08-04 11:48 ` Mykyta Yatsenko
2026-08-05 20:23 ` Steven Rostedt [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-07-30 15:00 Mark Brown
2026-07-31 22:03 ` Linus Walleij
2026-07-13 16:48 Mark Brown
2026-07-13 18:46 ` Tyrel Datwyler
2026-07-02 18:26 Mark Brown
2026-07-03 5:04 ` Kir Chou
2026-06-15 14:43 Mark Brown
2026-06-15 16:21 ` Mark Brown
2026-05-18 16:21 Mark Brown
2026-05-18 19:24 ` Nathan Chancellor
2026-05-18 20:06 ` Linus Torvalds
2026-04-01 14:07 Mark Brown
2026-03-27 22:01 Mark Brown
2026-03-27 22:03 ` Mark Brown
2026-03-27 22:05 ` Mark Brown
2026-03-28 2:18 ` Steven Rostedt
2026-03-26 16:04 Mark Brown
2026-03-26 17:05 ` Danilo Krummrich
2026-01-19 22:30 Mark Brown
2026-01-19 22:37 ` Miguel Ojeda
2026-01-19 23:32 ` Mark Brown
2026-01-19 22:49 ` Danilo Krummrich
2026-01-20 8:36 ` Alice Ryhl
2026-01-20 10:01 ` Danilo Krummrich
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=20260805162327.4dee0a76@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=mykyta.yatsenko5@gmail.com \
--cc=yatsenko@meta.com \
/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