From: kbuild test robot <lkp@intel.com>
To: Anshuman Khandual <anshuman.khandual@arm.com>
Cc: kbuild-all@lists.01.org,
Christophe Leroy <christophe.leroy@c-s.fr>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>
Subject: [linux-next:master 4446/4746] include/asm-generic/pgtable.h:1193: Error: Unknown opcode: `static'
Date: Tue, 15 Oct 2019 18:32:58 +0800 [thread overview]
Message-ID: <201910151856.cU8KHi7y%lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1305 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: 4eeb5abd245d849a4692325339a94566953363d6
commit: e3bcb4e7474a0e671e89ed5f731973287376b754 [4446/4746] mm/debug: add tests validating architecture page table helpers
config: parisc-c3000_defconfig (attached as .config)
compiler: hppa-linux-gcc (GCC) 7.4.0
reproduce:
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
git checkout e3bcb4e7474a0e671e89ed5f731973287376b754
# save the attached .config to linux build tree
GCC_VERSION=7.4.0 make.cross ARCH=parisc
If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
include/asm-generic/pgtable.h: Assembler messages:
>> include/asm-generic/pgtable.h:1193: Error: Unknown opcode: `static'
vim +1193 include/asm-generic/pgtable.h
1189
1190 #ifdef CONFIG_DEBUG_VM_PGTABLE
1191 extern void debug_vm_pgtable(void);
1192 #else
> 1193 static inline void debug_vm_pgtable(void) { }
1194 #endif
1195
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 15689 bytes --]
reply other threads:[~2019-10-15 10:34 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=201910151856.cU8KHi7y%lkp@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=anshuman.khandual@arm.com \
--cc=christophe.leroy@c-s.fr \
--cc=kbuild-all@lists.01.org \
--cc=linux-mm@kvack.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox