From: David Hildenbrand <david@redhat.com>
To: Wei Yang <richardw.yang@linux.intel.com>,
akpm@linux-foundation.org, cai@lca.pw
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [Patch v2] mm: remove dead code totalram_pages_set()
Date: Wed, 18 Dec 2019 09:46:58 +0100 [thread overview]
Message-ID: <20795dc0-8f6c-73cd-c98f-636f4ac59154@redhat.com> (raw)
In-Reply-To: <20191218005543.24146-1-richardw.yang@linux.intel.com>
On 18.12.19 01:55, Wei Yang wrote:
> No one uses totalram_pages_set(), just remove it.
>
> Fixes: ca79b0c211af ("mm: convert totalram_pages and totalhigh_pages
> variables to atomic")
Hi Wei, thanks for the update.
We should really avoid "Fixes" tags here. This is neither a bugfix nor a
compile fix.
@Andrew, can you fix that up to:
"Last user was removed in commit ca79b0c211af ("mm: convert
totalram_pages and totalhigh_pages variables to atomic")."
Cheers!
>
> Signed-off-by: Wei Yang <richardw.yang@linux.intel.com>
> Reviewed-by: David Hildenbrand <david@redhat.com>
>
> ---
> v2: fix typo and points which commit introduce it.
> ---
> include/linux/mm.h | 5 -----
> 1 file changed, 5 deletions(-)
>
> diff --git a/include/linux/mm.h b/include/linux/mm.h
> index 74232b28949b..4cf023c4c6b3 100644
> --- a/include/linux/mm.h
> +++ b/include/linux/mm.h
> @@ -70,11 +70,6 @@ static inline void totalram_pages_add(long count)
> atomic_long_add(count, &_totalram_pages);
> }
>
> -static inline void totalram_pages_set(long val)
> -{
> - atomic_long_set(&_totalram_pages, val);
> -}
> -
> extern void * high_memory;
> extern int page_cluster;
>
>
--
Thanks,
David / dhildenb
next prev parent reply other threads:[~2019-12-18 8:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-18 0:55 [Patch v2] mm: remove dead code totalram_pages_set() Wei Yang
2019-12-18 8:46 ` David Hildenbrand [this message]
2019-12-19 2:56 ` 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=20795dc0-8f6c-73cd-c98f-636f4ac59154@redhat.com \
--to=david@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=cai@lca.pw \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=richardw.yang@linux.intel.com \
/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).