From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Alice Ryhl <aliceryhl@google.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Matthew Maurer <mmaurer@google.com>,
Sami Tolvanen <samitolvanen@google.com>,
Gatlin Newhouse <gatlin.newhouse@gmail.com>,
Kees Cook <kees@kernel.org>,
"Peter Zijlstra (Intel)" <peterz@infradead.org>,
Miguel Ojeda <ojeda@kernel.org>,
Andrey Konovalov <andreyknvl@gmail.com>,
Marco Elver <elver@google.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 Linus' tree
Date: Thu, 26 Sep 2024 18:13:48 +1000 [thread overview]
Message-ID: <20240926181348.3965b040@canb.auug.org.au> (raw)
In-Reply-To: <CAH5fLgjRVZA3Gmb7Ogs+Y65T38EpNVeVEqmg93ZB4dn0Y7J3aA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 339 bytes --]
Hi Alice,
On Thu, 26 Sep 2024 09:36:56 +0200 Alice Ryhl <aliceryhl@google.com> wrote:
>
> Sorry about that! The fix is here:
> https://lore.kernel.org/all/20240925141944.277936-1-ojeda@kernel.org/
Thanks. I will replace the reverts in my fixes tree with that until it
is applied to Linus' tree.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2024-09-26 8:13 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-26 0:04 linux-next: build failure after merge of Linus' tree Stephen Rothwell
2024-09-26 7:36 ` Alice Ryhl
2024-09-26 8:13 ` Stephen Rothwell [this message]
2024-09-26 8:24 ` Miguel Ojeda
2024-09-26 12:49 ` Sedat Dilek
2024-09-26 12:58 ` Miguel Ojeda
2024-09-26 14:44 ` Sedat Dilek
2024-09-26 14:57 ` Miguel Ojeda
-- strict thread matches above, loose matches on Subject: below --
2025-02-03 1:59 Stephen Rothwell
2025-02-03 2:56 ` Jens Axboe
2020-04-20 11:35 Stephen Rothwell
2016-08-08 1:58 Stephen Rothwell
2016-08-08 15:37 ` Doug Ledford
2016-08-08 21:53 ` Stephen Rothwell
2016-08-08 23:30 ` Doug Ledford
2016-08-08 23:59 ` Stephen Rothwell
2016-08-09 8:54 ` Leon Romanovsky
2016-08-09 12:45 ` Doug Ledford
2015-10-07 22:44 Stephen Rothwell
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=20240926181348.3965b040@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=aliceryhl@google.com \
--cc=andreyknvl@gmail.com \
--cc=elver@google.com \
--cc=gatlin.newhouse@gmail.com \
--cc=kees@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mmaurer@google.com \
--cc=ojeda@kernel.org \
--cc=peterz@infradead.org \
--cc=samitolvanen@google.com \
--cc=torvalds@linux-foundation.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