[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <49a53674-f246-fdd6-009b-447a88cdb68e@redhat.com>
Date: Thu, 9 Jul 2020 11:18:57 +0200
From: David Hildenbrand <david@...hat.com>
To: Mike Rapoport <rppt@...ux.ibm.com>,
Matthew Wilcox <willy@...radead.org>
Cc: Jia He <justin.he@....com>,
Catalin Marinas <catalin.marinas@....com>,
Will Deacon <will@...nel.org>, Tony Luck <tony.luck@...el.com>,
Fenghua Yu <fenghua.yu@...el.com>,
Yoshinori Sato <ysato@...rs.sourceforge.jp>,
Rich Felker <dalias@...c.org>,
Dave Hansen <dave.hansen@...ux.intel.com>,
Andy Lutomirski <luto@...nel.org>,
Peter Zijlstra <peterz@...radead.org>,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>, Borislav Petkov <bp@...en8.de>,
x86@...nel.org, "H. Peter Anvin" <hpa@...or.com>,
Dan Williams <dan.j.williams@...el.com>,
Vishal Verma <vishal.l.verma@...el.com>,
Dave Jiang <dave.jiang@...el.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Baoquan He <bhe@...hat.com>,
Chuhong Yuan <hslester96@...il.com>,
Logan Gunthorpe <logang@...tatee.com>,
Masahiro Yamada <masahiroy@...nel.org>,
Michal Hocko <mhocko@...e.com>,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
linux-ia64@...r.kernel.org, linux-sh@...r.kernel.org,
linux-nvdimm@...ts.01.org, linux-mm@...ck.org,
Jonathan Cameron <Jonathan.Cameron@...wei.com>,
Kaly Xin <Kaly.Xin@....com>
Subject: Re: [PATCH v3 4/6] mm: don't export memory_add_physaddr_to_nid in
arch specific directory
On 09.07.20 11:18, Mike Rapoport wrote:
> On Thu, Jul 09, 2020 at 03:11:04AM +0100, Matthew Wilcox wrote:
>> On Thu, Jul 09, 2020 at 10:06:27AM +0800, Jia He wrote:
>>> After a general version of __weak memory_add_physaddr_to_nid implemented
>>> and exported , it is no use exporting twice in arch directory even if
>>> e,g, ia64/x86 have their specific version.
>>>
>>> This is to suppress the modpost warning:
>>> WARNING: modpost: vmlinux: 'memory_add_physaddr_to_nid' exported twice.
>>> Previous export was in vmlinux
>>
>> It's bad form to introduce a warning and then send a follow-up patch to
>> fix the warning. Just fold this patch into patch 1/6.
>
> Moreover, I think that patches 1-4 can be merged into one.
>
+1
--
Thanks,
David / dhildenb
Powered by blists - more mailing lists