From: David Hildenbrand <david@redhat.com>
To: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>,
Oscar Salvador <osalvador@suse.de>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Vlastimil Babka <vbabka@suse.cz>,
Jonathan Cameron <Jonathan.Cameron@huawei.com>,
Harry Yoo <harry.yoo@oracle.com>, Rakie Kim <rakie.kim@sk.com>,
Hyeonggon Yoo <42.hyeyoo@gmail.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 00/10]
Date: Fri, 6 Jun 2025 13:46:03 +0200 [thread overview]
Message-ID: <1ef7699b-d094-4ade-966f-d17f4d9a3613@redhat.com> (raw)
In-Reply-To: <c4a96aa2-10ae-4dc1-abd8-be91f7e8b583@lucifer.local>
On 06.06.25 13:30, Lorenzo Stoakes wrote:
> Hi Oscar,
>
> I don't have time to dig into what's broken here, but this series is breaking
> the mm-new build.
>
> NODE_REMOVED_LAST_MEMORY for instance doesn't seem to be defined, but there's a
> bunch more errors.
>
> Are you expecting stuff to land from other trees that isn't merged in Andrew's
> tree yet? Maybe from slab tree?
(David replying)
no, this is standalone, and probably just an error in the patches.
IIUC, the build bots reported this this night as reply to patch #4.
--
Cheers,
David / dhildenb
next prev parent reply other threads:[~2025-06-06 11:46 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-05 14:22 [PATCH v5 00/10] Oscar Salvador
2025-06-05 14:22 ` [PATCH v5 01/10] mm,slub: Do not special case N_NORMAL nodes for slab_nodes Oscar Salvador
2025-06-05 14:22 ` [PATCH v5 02/10] mm,memory_hotplug: Remove status_change_nid_normal and update documentation Oscar Salvador
2025-06-05 14:34 ` Vlastimil Babka
2025-06-05 14:54 ` David Hildenbrand
2025-06-05 15:49 ` Oscar Salvador
2025-06-05 14:22 ` [PATCH v5 03/10] mm,memory_hotplug: Implement numa node notifier Oscar Salvador
2025-06-06 7:50 ` Oscar Salvador
2025-06-05 14:22 ` [PATCH v5 04/10] mm,slub: Use node-notifier instead of memory-notifier Oscar Salvador
2025-06-06 1:50 ` kernel test robot
2025-06-06 7:51 ` Oscar Salvador
2025-06-06 11:56 ` David Hildenbrand
2025-06-06 12:28 ` Oscar Salvador
2025-06-06 12:35 ` David Hildenbrand
2025-06-05 14:22 ` [PATCH v5 05/10] mm,memory-tiers: " Oscar Salvador
2025-06-06 11:50 ` David Hildenbrand
2025-06-05 14:22 ` [PATCH v5 06/10] drivers,cxl: " Oscar Salvador
2025-06-06 11:51 ` David Hildenbrand
2025-06-05 14:22 ` [PATCH v5 07/10] drivers,hmat: " Oscar Salvador
2025-06-06 11:51 ` David Hildenbrand
2025-06-07 22:59 ` Andrew Morton
2025-06-05 14:22 ` [PATCH v5 08/10] kernel,cpuset: " Oscar Salvador
2025-06-06 11:52 ` David Hildenbrand
2025-06-05 14:23 ` [PATCH v5 09/10] mm,mempolicy: " Oscar Salvador
2025-06-09 6:47 ` Rakie Kim
2025-06-05 14:23 ` [PATCH v5 10/10] mm,memory_hotplug: Rename status_change_nid parameter in memory_notify Oscar Salvador
2025-06-06 11:48 ` David Hildenbrand
2025-06-06 11:30 ` [PATCH v5 00/10] Lorenzo Stoakes
2025-06-06 11:46 ` David Hildenbrand [this message]
2025-06-06 12:31 ` Oscar Salvador
2025-06-06 12:45 ` Lorenzo Stoakes
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=1ef7699b-d094-4ade-966f-d17f4d9a3613@redhat.com \
--to=david@redhat.com \
--cc=42.hyeyoo@gmail.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=harry.yoo@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=osalvador@suse.de \
--cc=rakie.kim@sk.com \
--cc=vbabka@suse.cz \
/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;
as well as URLs for NNTP newsgroup(s).