From: kbuild test robot <lkp@intel.com>
To: kbuild@lists.01.org
Subject: [ihalip:KSPP20 1/1] arch/x86/mm/pti.c:74:8: warning: syntax error [syntaxError]
Date: Fri, 24 Apr 2020 12:36:20 +0800 [thread overview]
Message-ID: <202004241215.KM0i7THs%lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1665 bytes --]
CC: kbuild-all(a)lists.01.org
TO: Ilie Halip <ilie.halip@gmail.com>
tree: https://github.com/ihalip/linux KSPP20
head: 8330d5d8175290b95261a95dddf7f914740d4dbb
commit: 8330d5d8175290b95261a95dddf7f914740d4dbb [1/1] mark some variables as __ro_after_init
:::::: branch date: 15 hours ago
:::::: commit date: 15 hours ago
If you fix the issue, kindly add following tag as appropriate
Reported-by: kbuild test robot <lkp@intel.com>
cppcheck warnings: (new ones prefixed by >>)
>> arch/x86/mm/pti.c:74:8: warning: syntax error [syntaxError]
static enum pti_mode {
^
# https://github.com/ihalip/linux/commit/8330d5d8175290b95261a95dddf7f914740d4dbb
git remote add ihalip https://github.com/ihalip/linux
git remote update ihalip
git checkout 8330d5d8175290b95261a95dddf7f914740d4dbb
vim +74 arch/x86/mm/pti.c
41f4c20b57a489 Borislav Petkov 2017-12-12 73
4fe64a62e04cfb Valdis Kletnieks 2019-03-12 @74 static enum pti_mode {
8c06c7740d191b Dave Hansen 2018-04-06 75 PTI_AUTO = 0,
8c06c7740d191b Dave Hansen 2018-04-06 76 PTI_FORCE_OFF,
8c06c7740d191b Dave Hansen 2018-04-06 77 PTI_FORCE_ON
8330d5d8175290 Ilie Halip 2020-04-15 78 } pti_mode __ro_after_init;
8c06c7740d191b Dave Hansen 2018-04-06 79
:::::: The code at line 74 was first introduced by commit
:::::: 4fe64a62e04cfb2dc1daab0d8f05d212aa014161 x86/mm/pti: Make local symbols static
:::::: TO: Valdis Kletnieks <valdis.kletnieks@vt.edu>
:::::: CC: Thomas Gleixner <tglx@linutronix.de>
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org
reply other threads:[~2020-04-24 4:36 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=202004241215.KM0i7THs%lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild@lists.01.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.