linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Omar Sandoval <osandov@osandov.com>
To: Israel Batista <linux@israelbatista.dev.br>
Cc: akpm@linux-foundation.org, david@redhat.com, linux-mm@kvack.org,
	linux-debuggers@vger.kernel.org
Subject: Re: [PATCH] mm: Convert memory block states (MEM_*) macros to enum
Date: Mon, 27 Oct 2025 23:51:25 -0700	[thread overview]
Message-ID: <aQBn7Xsx2qi6YDWp@telecaster> (raw)
In-Reply-To: <391c924d-b6f4-429f-8190-b33e3b6a3942@israelbatista.dev.br>

On Mon, Oct 27, 2025 at 11:41:47PM +0000, Israel Batista wrote:
> 
> 
> On 10/27/25 15:18, Omar Sandoval wrote:
> > 
> > What kernel version is this patch based on? It doesn't apply on mainline
> > because it is missing a couple of definitions added in 6.9 by commit
> > c5f1e2d18909 ("mm/memory_hotplug: introduce
> > MEM_PREPARE_ONLINE/MEM_FINISH_OFFLINE notifiers").
> > 
> 
> Sorry, my bad. I mixed-up my local branches and created the patch from
> linux-next rather than Linus's tree. I will create a new patch with the
> proper changes.

Oh, linux-next is usually fine, too (different subsystems have different
preferences, and I don't know mm's preference). Regardless of what tree
you base it on, it's nice if you mention the base in the patch email
under the ---.

Thanks,
Omar


      reply	other threads:[~2025-10-28  6:51 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-26 16:22 Israel Batista
2025-10-27  9:29 ` David Hildenbrand
2025-10-27 18:15   ` Omar Sandoval
2025-10-27 19:16     ` David Hildenbrand
2025-10-27 19:46     ` Lorenzo Stoakes
2025-10-27 23:34       ` Omar Sandoval
2025-10-28 16:06         ` David Hildenbrand
2025-10-28 16:33         ` Lorenzo Stoakes
2025-10-28 17:40           ` Omar Sandoval
2025-10-27 23:53       ` Israel Batista
2025-10-28 16:34         ` Lorenzo Stoakes
2025-10-28 19:06           ` Israel Batista
2025-10-28 19:13             ` Lorenzo Stoakes
2025-10-27 18:18 ` Omar Sandoval
2025-10-27 19:17   ` David Hildenbrand
2025-10-27 23:41   ` Israel Batista
2025-10-28  6:51     ` Omar Sandoval [this message]

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=aQBn7Xsx2qi6YDWp@telecaster \
    --to=osandov@osandov.com \
    --cc=akpm@linux-foundation.org \
    --cc=david@redhat.com \
    --cc=linux-debuggers@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux@israelbatista.dev.br \
    /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