From: Peng Zhang <zhangpeng.00@bytedance.com>
To: rppt@kernel.org
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
akpm@linux-foundation.org
Subject: Re: [PATCH 3/3] memblock: Avoid useless checks in memblock_merge_regions().
Date: Tue, 17 Jan 2023 15:31:34 +0800 [thread overview]
Message-ID: <9f626aa0-cabe-8c7f-5a3c-b30ea52a6adb@bytedance.com> (raw)
In-Reply-To: <20230113082659.65276-4-zhangpeng.00@bytedance.com>
Hi, Mike
What's your opinion of this patch?
Sincerely yours,
Peng.
next prev parent reply other threads:[~2023-01-17 7:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-13 8:26 [PATCH 0/3] Some small improvements for memblock Peng Zhang
2023-01-13 8:26 ` [PATCH 1/3] memblock: Make a boundary tighter in memblock_add_range() Peng Zhang
2023-01-13 8:26 ` [PATCH 2/3] memblock: Make finding index faster when modify regions Peng Zhang
2023-01-15 14:02 ` Mike Rapoport
2023-01-16 3:17 ` Peng Zhang
2023-01-16 7:37 ` Mike Rapoport
2023-01-16 8:40 ` Peng Zhang
2023-01-19 13:00 ` Mike Rapoport
2023-01-13 8:26 ` [PATCH 3/3] memblock: Avoid useless checks in memblock_merge_regions() Peng Zhang
2023-01-17 7:31 ` Peng Zhang [this message]
2023-01-19 13:04 ` Mike Rapoport
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=9f626aa0-cabe-8c7f-5a3c-b30ea52a6adb@bytedance.com \
--to=zhangpeng.00@bytedance.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--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