From: Matthew Wilcox <willy@infradead.org>
To: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Uros Bizjak <ubizjak@gmail.com>, Miguel Ojeda <ojeda@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org, mm-commits@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] MM updates for 6.14-rc1
Date: Sun, 26 Jan 2025 21:19:45 +0000 [thread overview]
Message-ID: <Z5am8bRw4lSJY8jF@casper.infradead.org> (raw)
In-Reply-To: <CANiq72mC7Fr6pB-D_JT9A2gCc2Yr0TLf16eRyY4_UWqRrKNVZg@mail.gmail.com>
On Sun, Jan 26, 2025 at 09:28:09PM +0100, Miguel Ojeda wrote:
> I will add a couple distro builds for linux-next in my matrix, one
> including GCC, so that hopefully at least you don't get blocked with
> something like this.
FYI, this was picked up:
https://lore.kernel.org/all/CA+G9fYuP2bHnDvJwfMm6+8Y8UYk74qCw-2HsFyRzJDFiQ5dbpQ@mail.gmail.com/
But, I guess due to the xmas break, nobody figured it out. It even
went to the Rust list via Dan Carpenter's response.
next prev parent reply other threads:[~2025-01-26 21:19 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-25 0:22 Andrew Morton
2025-01-25 22:09 ` Linus Torvalds
2025-01-26 5:00 ` Andrew Morton
2025-01-26 7:34 ` Linus Torvalds
2025-01-26 8:27 ` Stephen Rothwell
2025-01-26 12:10 ` Uros Bizjak
2025-01-26 9:57 ` Uros Bizjak
2025-01-26 17:21 ` Uros Bizjak
2025-01-26 18:29 ` Linus Torvalds
2025-01-26 19:46 ` Uros Bizjak
2025-01-26 20:06 ` Uros Bizjak
2025-01-26 21:59 ` Linus Torvalds
2025-01-26 23:27 ` Uros Bizjak
2025-01-27 0:08 ` Linus Torvalds
2025-01-27 7:29 ` Uros Bizjak
2025-01-26 20:28 ` Miguel Ojeda
2025-01-26 21:19 ` Matthew Wilcox [this message]
2025-01-26 21:35 ` Miguel Ojeda
2025-01-26 20:58 ` Miguel Ojeda
2025-01-29 20:10 ` John Hubbard
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=Z5am8bRw4lSJY8jF@casper.infradead.org \
--to=willy@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=miguel.ojeda.sandonis@gmail.com \
--cc=mm-commits@vger.kernel.org \
--cc=ojeda@kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=ubizjak@gmail.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