From: Oscar Salvador <osalvador@suse.de>
To: Wei Yang <richard.weiyang@gmail.com>
Cc: rppt@kernel.org, akpm@linux-foundation.org, linux-mm@kvack.org,
Pavel Tatashin <pasha.tatashin@oracle.com>
Subject: Re: [PATCH] mm/sparse: guard the size of mem_section is power of 2
Date: Tue, 16 Apr 2024 06:55:44 +0200 [thread overview]
Message-ID: <Zh4E0LpDvoFl1S6R@localhost.localdomain> (raw)
In-Reply-To: <20240416012559.4536-1-richard.weiyang@gmail.com>
On Tue, Apr 16, 2024 at 01:25:59AM +0000, Wei Yang wrote:
> We usually have this check, while commit 2a3cb8baef71 ("mm/sparse:
> delete old sparse_init and enable new one") missed to take it.
>
> Signed-off-by: Wei Yang <richard.weiyang@gmail.com>
> CC: Pavel Tatashin <pasha.tatashin@oracle.com>
Acked-by: Oscar Salvador <osalvador@suse.de>
--
Oscar Salvador
SUSE Labs
next prev parent reply other threads:[~2024-04-16 4:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-16 1:25 [PATCH] mm/sparse: guard the size of mem_section is power of 2 Wei Yang
2024-04-16 4:55 ` Oscar Salvador [this message]
2024-04-16 15:20 ` Pasha Tatashin
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=Zh4E0LpDvoFl1S6R@localhost.localdomain \
--to=osalvador@suse.de \
--cc=akpm@linux-foundation.org \
--cc=linux-mm@kvack.org \
--cc=pasha.tatashin@oracle.com \
--cc=richard.weiyang@gmail.com \
--cc=rppt@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;
as well as URLs for NNTP newsgroup(s).