From: David Hildenbrand <david@redhat.com>
To: Anshuman Khandual <anshuman.khandual@arm.com>, linux-mm@kvack.org
Cc: Dan Williams <dan.j.williams@intel.com>,
Andrew Morton <akpm@linux-foundation.org>,
Jason Gunthorpe <jgg@ziepe.ca>,
Logan Gunthorpe <logang@deltatee.com>,
Ira Weiny <ira.weiny@intel.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm/memremap: Drop unused SECTION_SIZE and SECTION_MASK
Date: Tue, 24 Sep 2019 10:35:51 +0200 [thread overview]
Message-ID: <557ceba1-9cf3-203c-cbb4-27cae68e0b90@redhat.com> (raw)
In-Reply-To: <1569312010-31313-1-git-send-email-anshuman.khandual@arm.com>
On 24.09.19 10:00, Anshuman Khandual wrote:
> SECTION_SIZE and SECTION_MASK macros are not getting used anymore. But they
> do conflict with existing definitions on arm64 platform causing following
> warning during build. Lets drop these unused macros.
>
> mm/memremap.c:16: warning: "SECTION_MASK" redefined
> #define SECTION_MASK ~((1UL << PA_SECTION_SHIFT) - 1)
>
> In file included from ./arch/arm64/include/asm/processor.h:34,
> from ./include/linux/mutex.h:19,
> from ./include/linux/kernfs.h:12,
> from ./include/linux/sysfs.h:16,
> from ./include/linux/kobject.h:20,
> from ./include/linux/device.h:16,
> from mm/memremap.c:3:
> ./arch/arm64/include/asm/pgtable-hwdef.h:79: note: this is the location of
> the previous definition
> #define SECTION_MASK (~(SECTION_SIZE-1))
>
> mm/memremap.c:17: warning: "SECTION_SIZE" redefined
> #define SECTION_SIZE (1UL << PA_SECTION_SHIFT)
>
> In file included from ./arch/arm64/include/asm/processor.h:34,
> from ./include/linux/mutex.h:19,
> from ./include/linux/kernfs.h:12,
> from ./include/linux/sysfs.h:16,
> from ./include/linux/kobject.h:20,
> from ./include/linux/device.h:16,
> from mm/memremap.c:3:
> ./arch/arm64/include/asm/pgtable-hwdef.h:78: note: this is the location of
> the previous definition
> #define SECTION_SIZE (_AC(1, UL) << SECTION_SHIFT)
>
> Cc: Dan Williams <dan.j.williams@intel.com>
> Cc: Andrew Morton <akpm@linux-foundation.org>
> Cc: Jason Gunthorpe <jgg@ziepe.ca>
> Cc: Logan Gunthorpe <logang@deltatee.com>
> Cc: Ira Weiny <ira.weiny@intel.com>
> Cc: linux-kernel@vger.kernel.org
> Reported-by: kbuild test robot <lkp@intel.com>
> Signed-off-by: Anshuman Khandual <anshuman.khandual@arm.com>
> ---
> Build and boot tested on arm64 platform with ZONE_DEVICE enabled. But
> only boot tested on arm64 and some other platforms with allmodconfig.
>
> mm/memremap.c | 2 --
> 1 file changed, 2 deletions(-)
>
> diff --git a/mm/memremap.c b/mm/memremap.c
> index f6c17339cd0d..bf2882bfbf48 100644
> --- a/mm/memremap.c
> +++ b/mm/memremap.c
> @@ -13,8 +13,6 @@
> #include <linux/xarray.h>
>
> static DEFINE_XARRAY(pgmap_array);
> -#define SECTION_MASK ~((1UL << PA_SECTION_SHIFT) - 1)
> -#define SECTION_SIZE (1UL << PA_SECTION_SHIFT)
>
> #ifdef CONFIG_DEV_PAGEMAP_OPS
> DEFINE_STATIC_KEY_FALSE(devmap_managed_key);
>
Reviewed-by: David Hildenbrand <david@redhat.com>
--
Thanks,
David / dhildenb
prev parent reply other threads:[~2019-09-24 8:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-24 8:00 Anshuman Khandual
2019-09-24 8:35 ` David Hildenbrand [this message]
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=557ceba1-9cf3-203c-cbb4-27cae68e0b90@redhat.com \
--to=david@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=anshuman.khandual@arm.com \
--cc=dan.j.williams@intel.com \
--cc=ira.weiny@intel.com \
--cc=jgg@ziepe.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=logang@deltatee.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
all inboxes | Powered by JetHome®