From: Mike Rapoport <rppt@kernel.org>
To: akpm@linux-foundation.org, Wei Yang <richard.weiyang@gmail.com>
Cc: Mike Rapoport <rppt@kernel.org>,
linux-mm@kvack.org, Paul Mackerras <paulus@ozlabs.org>,
Tejun Heo <tj@kernel.org>
Subject: Re: [Patch v3] mm/memblock: remove empty dummy entry
Date: Tue, 9 Apr 2024 08:02:51 +0300 [thread overview]
Message-ID: <171263893900.532217.7883690706896508109.b4-ty@kernel.org> (raw)
In-Reply-To: <20240405015821.13411-1-richard.weiyang@gmail.com>
From: Mike Rapoport (IBM) <rppt@kernel.org>
On Fri, 05 Apr 2024 01:58:21 +0000, Wei Yang wrote:
> The dummy entry is introduced in the initial implementation of lmb in
> commit 7c8c6b9776fb ("powerpc: Merge lmb.c and make MM initialization
> use it.").
>
> As the comment says the empty dummy entry is to simplify the code.
>
> /* Create a dummy zero size LMB which will get coalesced away later.
> * This simplifies the lmb_add() code below...
> */
>
> [...]
Applied to for-next branch of memblock.git tree, thanks!
[1/1] mm/memblock: remove empty dummy entry
commit: e5d1fdecfaf8470bad3874d00c7921e3883495b7
tree: https://git.kernel.org/pub/scm/linux/kernel/git/rppt/memblock
branch: for-next
--
Sincerely yours,
Mike.
next prev parent reply other threads:[~2024-04-09 5:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-05 1:58 Wei Yang
2024-04-08 5:44 ` Mike Rapoport
2024-04-08 12:37 ` Wei Yang
2024-04-09 5:02 ` Mike Rapoport [this message]
[not found] ` <8d6205d4-18fb-4e98-97e6-db226dcf48f3@roeck-us.net>
2024-06-21 1:07 ` Wei Yang
2024-06-21 2:34 ` Guenter Roeck
2024-06-21 23:06 ` Wei Yang
[not found] ` <2113ef59-0efd-4de2-83f7-f5940ce40fca@roeck-us.net>
2024-06-22 18:16 ` Mike Rapoport
2024-06-23 0:31 ` Wei Yang
2024-06-21 1:11 ` Wei Yang
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=171263893900.532217.7883690706896508109.b4-ty@kernel.org \
--to=rppt@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=linux-mm@kvack.org \
--cc=paulus@ozlabs.org \
--cc=richard.weiyang@gmail.com \
--cc=tj@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