From: Mike Rapoport <rppt@kernel.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Mike Rapoport <rppt@linux.ibm.com>
Subject: Re: [PATCH] mm: remove unused early_pfn_valid()
Date: Mon, 28 Sep 2020 17:49:00 +0300 [thread overview]
Message-ID: <20200928144900.GA2142832@kernel.org> (raw)
In-Reply-To: <20200923162915.26935-1-rppt@kernel.org>
ping?
On Wed, Sep 23, 2020 at 07:29:15PM +0300, Mike Rapoport wrote:
> From: Mike Rapoport <rppt@linux.ibm.com>
>
> The early_pfn_valid() macro is defined by it is never used.
> Remove it.
>
> Signed-off-by: Mike Rapoport <rppt@linux.ibm.com>
> ---
> include/linux/mmzone.h | 5 -----
> 1 file changed, 5 deletions(-)
>
> diff --git a/include/linux/mmzone.h b/include/linux/mmzone.h
> index 8379432f4f2f..38264363b0d4 100644
> --- a/include/linux/mmzone.h
> +++ b/include/linux/mmzone.h
> @@ -1376,7 +1376,6 @@ static inline unsigned long next_present_section_nr(unsigned long section_nr)
> #define pfn_to_nid(pfn) (0)
> #endif
>
> -#define early_pfn_valid(pfn) pfn_valid(pfn)
> void sparse_init(void);
> #else
> #define sparse_init() do {} while (0)
> @@ -1396,10 +1395,6 @@ struct mminit_pfnnid_cache {
> int last_nid;
> };
>
> -#ifndef early_pfn_valid
> -#define early_pfn_valid(pfn) (1)
> -#endif
> -
> /*
> * If it is possible to have holes within a MAX_ORDER_NR_PAGES, then we
> * need to check pfn validity within that MAX_ORDER_NR_PAGES block.
> --
> 2.28.0
>
--
Sincerely yours,
Mike.
next prev parent reply other threads:[~2020-09-28 14:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-23 16:29 [PATCH] mm: remove unused early_pfn_valid() Mike Rapoport
2020-09-25 12:21 ` David Hildenbrand
2020-09-28 14:49 ` Mike Rapoport [this message]
2020-09-28 23:36 ` Andrew Morton
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=20200928144900.GA2142832@kernel.org \
--to=rppt@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rppt@linux.ibm.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).