From: Mike Rapoport <rppt@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Daeseok Youn <daeseok.youn@gmail.com>,
David Hildenbrand <david@redhat.com>,
Mike Rapoport <rppt@linux.ibm.com>,
Mike Rapoport <rppt@kernel.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] memblock: remove return value of memblock_free_all()
Date: Tue, 9 Feb 2021 11:43:27 +0200 [thread overview]
Message-ID: <20210209094327.GB242749@kernel.org> (raw)
Hi Linus,
This a small cleanup in memblock for 5.12 merge window.
The following changes since commit 7c53f6b671f4aba70ff15e1b05148b10d58c2837:
Linux 5.11-rc3 (2021-01-10 14:34:50 -0800)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/rppt/memblock tags/memblock-v5.12-rc1
for you to fetch changes up to 097d43d8570457c1af9b09fab15412697b177f35:
mm: memblock: remove return value of memblock_free_all() (2021-01-14 15:29:11 +0200)
----------------------------------------------------------------
memblock: remove return value of memblock_free_all()
memblock_free_all() returns the total count of freed pages and its callers
used this value to update totalram_pages. This update is now anyway a part
of memblock_free_all() and its callers no longer check the return value, so
make memblock_free_all() void.
----------------------------------------------------------------
Daeseok Youn (1):
mm: memblock: remove return value of memblock_free_all()
include/linux/memblock.h | 2 +-
mm/memblock.c | 6 +-----
2 files changed, 2 insertions(+), 6 deletions(-)
--
Sincerely yours,
Mike.
next reply other threads:[~2021-02-09 9:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-09 9:43 Mike Rapoport [this message]
2021-02-10 1:17 ` [GIT PULL] memblock: remove return value of memblock_free_all() Linus Torvalds
2021-02-10 6:32 ` Mike Rapoport
2021-02-22 21:35 ` pr-tracker-bot
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=20210209094327.GB242749@kernel.org \
--to=rppt@kernel.org \
--cc=daeseok.youn@gmail.com \
--cc=david@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rppt@linux.ibm.com \
--cc=torvalds@linux-foundation.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).