From: kernel test robot <lkp@intel.com>
To: Muchun Song <songmuchun@bytedance.com>,
will@kernel.org, akpm@linux-foundation.org, david@redhat.com,
bodeddub@amazon.com, osalvador@suse.de, mike.kravetz@oracle.com,
rientjes@google.com
Cc: kbuild-all@lists.01.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH 2/3] mm: hugetlb: introduce arch_free_vmemmap_page
Date: Thu, 11 Mar 2021 08:15:40 +0800 [thread overview]
Message-ID: <202103110857.YOMPk8Ef-lkp@intel.com> (raw)
In-Reply-To: <20210310071535.35245-3-songmuchun@bytedance.com>
[-- Attachment #1: Type: text/plain, Size: 1859 bytes --]
Hi Muchun,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on next-20210310]
[cannot apply to hnaz-linux-mm/master arm64/for-next/core tip/x86/mm linus/master v5.12-rc2 v5.12-rc1 v5.11 v5.12-rc2]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch]
url: https://github.com/0day-ci/linux/commits/Muchun-Song/mm-bootmem_info-mark-register_page_bootmem_info_section-__init/20210310-161619
base: b01d57bfdc41c8f635b08b8a5af8a31217d46936
config: x86_64-randconfig-c002-20210310 (attached as .config)
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
reproduce (this is a W=1 build):
# https://github.com/0day-ci/linux/commit/92924b23a9f6de5bb478cea033cd2d39c227a6c5
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review Muchun-Song/mm-bootmem_info-mark-register_page_bootmem_info_section-__init/20210310-161619
git checkout 92924b23a9f6de5bb478cea033cd2d39c227a6c5
# save the attached .config to linux build tree
make W=1 ARCH=x86_64
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
>> mm/sparse-vmemmap.c:159:13: warning: no previous prototype for 'arch_free_vmemmap_page' [-Wmissing-prototypes]
159 | void __weak arch_free_vmemmap_page(struct page *page)
| ^~~~~~~~~~~~~~~~~~~~~~
vim +/arch_free_vmemmap_page +159 mm/sparse-vmemmap.c
158
> 159 void __weak arch_free_vmemmap_page(struct page *page)
160 {
161 free_reserved_page(page);
162 }
163
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 35443 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: kernel test robot <lkp@intel.com>
To: Muchun Song <songmuchun@bytedance.com>,
will@kernel.org, akpm@linux-foundation.org, david@redhat.com,
bodeddub@amazon.com, osalvador@suse.de, mike.kravetz@oracle.com,
rientjes@google.com
Cc: kbuild-all@lists.01.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH 2/3] mm: hugetlb: introduce arch_free_vmemmap_page
Date: Thu, 11 Mar 2021 08:15:40 +0800 [thread overview]
Message-ID: <202103110857.YOMPk8Ef-lkp@intel.com> (raw)
In-Reply-To: <20210310071535.35245-3-songmuchun@bytedance.com>
[-- Attachment #1: Type: text/plain, Size: 1859 bytes --]
Hi Muchun,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on next-20210310]
[cannot apply to hnaz-linux-mm/master arm64/for-next/core tip/x86/mm linus/master v5.12-rc2 v5.12-rc1 v5.11 v5.12-rc2]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch]
url: https://github.com/0day-ci/linux/commits/Muchun-Song/mm-bootmem_info-mark-register_page_bootmem_info_section-__init/20210310-161619
base: b01d57bfdc41c8f635b08b8a5af8a31217d46936
config: x86_64-randconfig-c002-20210310 (attached as .config)
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
reproduce (this is a W=1 build):
# https://github.com/0day-ci/linux/commit/92924b23a9f6de5bb478cea033cd2d39c227a6c5
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review Muchun-Song/mm-bootmem_info-mark-register_page_bootmem_info_section-__init/20210310-161619
git checkout 92924b23a9f6de5bb478cea033cd2d39c227a6c5
# save the attached .config to linux build tree
make W=1 ARCH=x86_64
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
>> mm/sparse-vmemmap.c:159:13: warning: no previous prototype for 'arch_free_vmemmap_page' [-Wmissing-prototypes]
159 | void __weak arch_free_vmemmap_page(struct page *page)
| ^~~~~~~~~~~~~~~~~~~~~~
vim +/arch_free_vmemmap_page +159 mm/sparse-vmemmap.c
158
> 159 void __weak arch_free_vmemmap_page(struct page *page)
160 {
161 free_reserved_page(page);
162 }
163
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 35443 bytes --]
[-- Attachment #3: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: Re: [PATCH 2/3] mm: hugetlb: introduce arch_free_vmemmap_page
Date: Thu, 11 Mar 2021 08:15:40 +0800 [thread overview]
Message-ID: <202103110857.YOMPk8Ef-lkp@intel.com> (raw)
In-Reply-To: <20210310071535.35245-3-songmuchun@bytedance.com>
[-- Attachment #1: Type: text/plain, Size: 1905 bytes --]
Hi Muchun,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on next-20210310]
[cannot apply to hnaz-linux-mm/master arm64/for-next/core tip/x86/mm linus/master v5.12-rc2 v5.12-rc1 v5.11 v5.12-rc2]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch]
url: https://github.com/0day-ci/linux/commits/Muchun-Song/mm-bootmem_info-mark-register_page_bootmem_info_section-__init/20210310-161619
base: b01d57bfdc41c8f635b08b8a5af8a31217d46936
config: x86_64-randconfig-c002-20210310 (attached as .config)
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
reproduce (this is a W=1 build):
# https://github.com/0day-ci/linux/commit/92924b23a9f6de5bb478cea033cd2d39c227a6c5
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review Muchun-Song/mm-bootmem_info-mark-register_page_bootmem_info_section-__init/20210310-161619
git checkout 92924b23a9f6de5bb478cea033cd2d39c227a6c5
# save the attached .config to linux build tree
make W=1 ARCH=x86_64
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
>> mm/sparse-vmemmap.c:159:13: warning: no previous prototype for 'arch_free_vmemmap_page' [-Wmissing-prototypes]
159 | void __weak arch_free_vmemmap_page(struct page *page)
| ^~~~~~~~~~~~~~~~~~~~~~
vim +/arch_free_vmemmap_page +159 mm/sparse-vmemmap.c
158
> 159 void __weak arch_free_vmemmap_page(struct page *page)
160 {
161 free_reserved_page(page);
162 }
163
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org
[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 35443 bytes --]
next prev parent reply other threads:[~2021-03-11 0:16 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-10 7:15 [PATCH 0/3] Add support for free vmemmap pages of HugeTLB for arm64 Muchun Song
2021-03-10 7:15 ` Muchun Song
2021-03-10 7:15 ` [PATCH 1/3] mm: bootmem_info: mark register_page_bootmem_info_section __init Muchun Song
2021-03-10 7:15 ` Muchun Song
2021-03-10 7:15 ` [PATCH 2/3] mm: hugetlb: introduce arch_free_vmemmap_page Muchun Song
2021-03-10 7:15 ` Muchun Song
2021-03-10 12:16 ` kernel test robot
2021-03-10 12:16 ` kernel test robot
2021-03-10 12:16 ` kernel test robot
2021-03-11 0:15 ` kernel test robot [this message]
2021-03-11 0:15 ` kernel test robot
2021-03-11 0:15 ` kernel test robot
2021-03-10 7:15 ` [PATCH 3/3] arm64: mm: hugetlb: add support for free vmemmap pages of HugeTLB Muchun Song
2021-03-10 7:15 ` Muchun Song
2021-03-11 0:47 ` kernel test robot
2021-03-11 0:47 ` kernel test robot
2021-03-11 0:47 ` kernel test robot
2021-03-11 4:12 ` [PATCH 0/3] Add support for free vmemmap pages of HugeTLB for arm64 Chen Huang
2021-03-11 4:12 ` Chen Huang
2021-03-11 5:00 ` Bodeddula, Balasubramaniam
2021-03-11 5:00 ` Bodeddula, Balasubramaniam
2021-03-11 5:00 ` Bodeddula, Balasubramaniam
2021-03-11 6:01 ` Chen Huang
2021-03-11 6:01 ` Chen Huang
2021-03-11 6:01 ` Chen Huang
2021-03-11 18:00 ` Bodeddula, Balasubramaniam
2021-03-11 18:00 ` Bodeddula, Balasubramaniam
2021-03-11 18:00 ` Bodeddula, Balasubramaniam
2021-03-12 2:52 ` Chen Huang
2021-03-12 2:52 ` Chen Huang
2021-03-12 2:52 ` Chen Huang
2021-03-12 17:38 ` Mike Kravetz
2021-03-12 17:38 ` Mike Kravetz
2021-03-12 17:38 ` Mike Kravetz
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=202103110857.YOMPk8Ef-lkp@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=bodeddub@amazon.com \
--cc=david@redhat.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mike.kravetz@oracle.com \
--cc=osalvador@suse.de \
--cc=rientjes@google.com \
--cc=songmuchun@bytedance.com \
--cc=will@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.