From: "David Hildenbrand (Arm)" <david@kernel.org>
To: Mark Brown <broonie@kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Ryan Roberts <ryan.roberts@arm.com>,
Will Deacon <will@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 mm-hotfixes tree
Date: Tue, 21 Apr 2026 15:42:29 +0200 [thread overview]
Message-ID: <a3b85bc7-d9b1-444b-8474-91d0e7f2a41d@kernel.org> (raw)
In-Reply-To: <2efaf5cb-abe1-4eaf-b269-bf303b7b8372@sirena.org.uk>
On 4/21/26 15:34, Mark Brown wrote:
> On Tue, Apr 21, 2026 at 02:21:48PM +0100, Mark Brown wrote:
>> On Tue, Apr 21, 2026 at 03:06:32PM +0200, David Hildenbrand (Arm) wrote:
>
>>
>> The commit is also present in the mm-unstable tree, I have also used
>> the version of that from 20260420.
>
> And similarly for the mm-nonmm-unstable tree.
I think Andrew uses the hotfixes tree as the base for the -unstable
trees. So anything that ends up in there gets fast-tracked into -next.
Not good :(
--
Cheers,
David
next prev parent reply other threads:[~2026-04-21 13:42 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-21 12:59 linux-next: build failure after merge of the mm-hotfixes tree Mark Brown
2026-04-21 13:06 ` David Hildenbrand (Arm)
2026-04-21 13:21 ` Mark Brown
2026-04-21 13:28 ` David Hildenbrand (Arm)
2026-04-21 13:34 ` Mark Brown
2026-04-21 13:42 ` David Hildenbrand (Arm) [this message]
2026-04-21 14:17 ` Andrew Morton
2026-04-21 14:20 ` David Hildenbrand (Arm)
2026-04-21 14:28 ` Andrew Morton
2026-04-21 14:35 ` David Hildenbrand (Arm)
2026-04-21 14:48 ` Andrew Morton
2026-04-21 15:04 ` David Hildenbrand (Arm)
2026-04-21 16:04 ` Philip Li
2026-04-21 16:21 ` David Hildenbrand (Arm)
2026-04-21 14:28 ` Mark Brown
2026-04-21 14:39 ` David Hildenbrand (Arm)
-- strict thread matches above, loose matches on Subject: below --
2025-12-07 21:35 Stephen Rothwell
2025-12-08 10:30 ` Maciej Wieczor-Retman
2025-12-09 1:37 ` Andrew Morton
2025-08-21 6:05 Stephen Rothwell
2025-08-21 9:49 ` Harry Yoo
2025-05-28 23:59 Stephen Rothwell
2025-05-29 0:02 ` Andrew Morton
2025-05-29 1:57 ` Stephen Rothwell
2025-05-29 0:03 ` Stephen Rothwell
2024-07-01 0:16 Stephen Rothwell
2024-07-01 1:01 ` Stephen Rothwell
2024-07-01 18:15 ` Yang Shi
2024-07-02 22:44 ` Stephen Rothwell
2024-07-02 23:22 ` Stephen Rothwell
2024-07-03 0:40 ` Yang Shi
2023-12-13 22:18 Stephen Rothwell
2023-12-13 23:31 ` Liam R. Howlett
2022-12-12 22:30 Stephen Rothwell
2022-12-13 1:34 ` Kefeng Wang
2022-12-13 2:23 ` Andrew Morton
2022-12-13 2:45 ` Stephen Rothwell
2022-12-13 2:54 ` Kefeng Wang
2022-11-25 1:10 Stephen Rothwell
2022-11-25 5:24 ` Juergen Gross
2022-11-25 5:24 ` Andrew Morton
2022-11-25 5:48 ` 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=a3b85bc7-d9b1-444b-8474-91d0e7f2a41d@kernel.org \
--to=david@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=ryan.roberts@arm.com \
--cc=will@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