From: Sasha Levin <sashal@kernel.org>
To: Mike Rapoport <rppt@kernel.org>
Cc: stable@vger.kernel.org, stable-commits@vger.kernel.org,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
Dave Hansen <dave.hansen@linux.intel.com>,
Andy Lutomirski <luto@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
x86@kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: Patch "mm: memblock: replace dereferences of memblock_region.nid with API calls" has been added to the 5.4-stable tree
Date: Thu, 27 Jun 2024 10:12:46 -0400 [thread overview]
Message-ID: <Zn1zXiis-yqRB2VO@sashalap> (raw)
In-Reply-To: <Zn0Q_DKvcVF8P5f-@kernel.org>
On Thu, Jun 27, 2024 at 10:13:00AM +0300, Mike Rapoport wrote:
>Hi Sasha,
>
>On Wed, Jun 26, 2024 at 03:07:08PM -0400, Sasha Levin wrote:
>> This is a note to let you know that I've just added the patch titled
>>
>> mm: memblock: replace dereferences of memblock_region.nid with API calls
>>
>> to the 5.4-stable tree which can be found at:
>> http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
>>
>> The filename of the patch is:
>> mm-memblock-replace-dereferences-of-memblock_region..patch
>> and it can be found in the queue-5.4 subdirectory.
>>
>> If you, or anyone else, feels it should not be added to the stable tree,
>> please let <stable@vger.kernel.org> know about it.
>>
>>
>>
>> commit dd8d9169375a725cadd5e3635342a6e2d483cf4c
>> Author: Mike Rapoport <rppt@kernel.org>
>> Date: Wed Jun 3 15:56:53 2020 -0700
>>
>> mm: memblock: replace dereferences of memblock_region.nid with API calls
>>
>> Stable-dep-of: 3ac36aa73073 ("x86/mm/numa: Use NUMA_NO_NODE when calling memblock_set_node()")
>
>The commit 3ac36aa73073 shouldn't be backported to 5.4 or anything before
>6.8 for that matter, I don't see a need to bring this in as well.
Sadly there was no fixes tag :(
Should this be reverted from 5.4 and older, or is it ok for it to be
there?
--
Thanks,
Sasha
next prev parent reply other threads:[~2024-06-27 14:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240626190708.2059584-1-sashal@kernel.org>
2024-06-27 7:13 ` Patch "mm: memblock: replace dereferences of memblock_region.nid with API calls" has been added to the 5.4-stable tree Mike Rapoport
2024-06-27 14:12 ` Sasha Levin [this message]
2024-06-27 14:40 ` Mike Rapoport
2024-06-27 19:55 ` Sasha Levin
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=Zn1zXiis-yqRB2VO@sashalap \
--to=sashal@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=bp@alien8.de \
--cc=catalin.marinas@arm.com \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rppt@kernel.org \
--cc=stable-commits@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=will@kernel.org \
--cc=x86@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