From: kernel test robot <lkp@intel.com>
To: Anshuman Khandual <anshuman.khandual@arm.com>, linux-mm@kvack.org
Cc: oe-kbuild-all@lists.linux.dev,
Anshuman Khandual <anshuman.khandual@arm.com>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>,
David Hildenbrand <david@redhat.com>,
Ryan Roberts <ryan.roberts@arm.com>,
"Mike Rapoport (IBM)" <rppt@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH V2] mm: Drop unused set_pte_safe()
Date: Fri, 13 Sep 2024 12:37:30 +0800 [thread overview]
Message-ID: <202409131214.d09v9mIO-lkp@intel.com> (raw)
In-Reply-To: <20240910101026.428808-1-anshuman.khandual@arm.com>
Hi Anshuman,
kernel test robot noticed the following build errors:
[auto build test ERROR on akpm-mm/mm-everything]
url: https://github.com/intel-lab-lkp/linux/commits/Anshuman-Khandual/mm-Drop-unused-set_pte_safe/20240910-181151
base: https://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm.git mm-everything
patch link: https://lore.kernel.org/r/20240910101026.428808-1-anshuman.khandual%40arm.com
patch subject: [PATCH V2] mm: Drop unused set_pte_safe()
config: x86_64-defconfig (https://download.01.org/0day-ci/archive/20240913/202409131214.d09v9mIO-lkp@intel.com/config)
compiler: gcc-11 (Debian 11.3.0-12) 11.3.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240913/202409131214.d09v9mIO-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202409131214.d09v9mIO-lkp@intel.com/
All errors (new ones prefixed by >>):
arch/x86/mm/init_64.c: In function 'set_pte_init':
>> arch/x86/mm/init_64.c:83:17: error: implicit declaration of function 'set_pte_safe'; did you mean 'set_pud_safe'? [-Werror=implicit-function-declaration]
83 | set_##type1##_safe(arg1, arg2); \
| ^~~~
arch/x86/mm/init_64.c:91:1: note: in expansion of macro 'DEFINE_ENTRY'
91 | DEFINE_ENTRY(pte, pte, init)
| ^~~~~~~~~~~~
cc1: some warnings being treated as errors
vim +83 arch/x86/mm/init_64.c
eccd906484d1cd Brijesh Singh 2019-04-17 77
eccd906484d1cd Brijesh Singh 2019-04-17 78 #define DEFINE_ENTRY(type1, type2, init) \
eccd906484d1cd Brijesh Singh 2019-04-17 79 static inline void set_##type1##_init(type1##_t *arg1, \
eccd906484d1cd Brijesh Singh 2019-04-17 80 type2##_t arg2, bool init) \
eccd906484d1cd Brijesh Singh 2019-04-17 81 { \
eccd906484d1cd Brijesh Singh 2019-04-17 82 if (init) \
eccd906484d1cd Brijesh Singh 2019-04-17 @83 set_##type1##_safe(arg1, arg2); \
eccd906484d1cd Brijesh Singh 2019-04-17 84 else \
eccd906484d1cd Brijesh Singh 2019-04-17 85 set_##type1(arg1, arg2); \
eccd906484d1cd Brijesh Singh 2019-04-17 86 }
eccd906484d1cd Brijesh Singh 2019-04-17 87
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2024-09-13 4:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-10 10:10 Anshuman Khandual
2024-09-10 20:13 ` Andrew Morton
2024-09-11 3:52 ` Anshuman Khandual
2024-09-13 4:16 ` kernel test robot
2024-09-13 4:37 ` kernel test robot [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=202409131214.d09v9mIO-lkp@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=anshuman.khandual@arm.com \
--cc=david@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=rppt@kernel.org \
--cc=ryan.roberts@arm.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