From: Andrew Morton <akpm@linux-foundation.org>
To: Hannes Reinecke <hare@suse.de>
Cc: Hannes Reinecke <hare@kernel.org>,
David Hildenbrand <david@redhat.com>,
Oscar Salvador <osalvador@suse.de>,
linux-mm@kvack.org
Subject: Re: [PATCHv4 0/3] mm/memory_hotplug: fixup crash during uevent handling
Date: Tue, 29 Jul 2025 23:30:56 -0700 [thread overview]
Message-ID: <20250729233056.c45b9c2e21ee7838434024c6@linux-foundation.org> (raw)
In-Reply-To: <907ee759-6051-4d47-bf09-cea362ac0cd9@suse.de>
On Wed, 30 Jul 2025 07:49:57 +0200 Hannes Reinecke <hare@suse.de> wrote:
> On 7/29/25 22:38, Andrew Morton wrote:
> > On Tue, 29 Jul 2025 08:46:33 +0200 Hannes Reinecke <hare@kernel.org> wrote:
> > be needed in earlier kernels?
> >
> > IOW, if we wish to fix this crash in earlier kernels, I really cant use
> > this series as presented. For now I'll add it to mm-new to get it a bit
> > of exposure while we decide what to do.
> >
> >
> And here's me who thought we were doing upstream work precisely to
> _not_ having to do backports :-)
Yeah, well, maybe others aren't as keen on caring for -stable but I do
think it's part of our role as kernel maintainers (as opposed to
"developers"?). And as a large number of MM developers work at
organizations which use and ship older kernel releases, I assume
they're on board with that!
> I see if we can roll patch 1&2 into one; guess I'll need to do it
> anyway for our kernel.
You too!
Thanks.
next prev parent reply other threads:[~2025-07-30 6:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-29 6:46 Hannes Reinecke
2025-07-29 6:46 ` [PATCH 1/3] drivers/base/memory: add node id parameter to add_memory_block() Hannes Reinecke
2025-07-29 6:46 ` [PATCH 2/3] mm/memory_hotplug: activate node before adding new memory blocks Hannes Reinecke
2025-07-29 6:46 ` [PATCH 3/3] drivers/base: move memory_block_add_nid() into the caller Hannes Reinecke
2025-07-29 20:38 ` [PATCHv4 0/3] mm/memory_hotplug: fixup crash during uevent handling Andrew Morton
2025-07-30 5:49 ` Hannes Reinecke
2025-07-30 6:30 ` Andrew Morton [this message]
2025-07-30 9:39 ` David Hildenbrand
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=20250729233056.c45b9c2e21ee7838434024c6@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=hare@kernel.org \
--cc=hare@suse.de \
--cc=linux-mm@kvack.org \
--cc=osalvador@suse.de \
/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