From: kernel test robot <lkp@intel.com>
To: Mauro Carvalho Chehab <mchehab@kernel.org>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
linux-media@vger.kernel.org
Subject: drivers/pinctrl/intel/pinctrl-intel.c:210: error: Cannot parse enum!
Date: Sun, 18 Oct 2020 12:41:21 +0800 [thread overview]
Message-ID: <202010181218.snceHRO0-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3124 bytes --]
Hi Mauro,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 9d9af1007bc08971953ae915d88dc9bb21344b53
commit: d38c8cfb057183f619dc8534030bb64b63f78043 scripts: kernel-doc: add support for typedef enum
date: 3 days ago
config: x86_64-rhel-7.6-kselftests (attached as .config)
compiler: gcc-9 (Debian 9.3.0-15) 9.3.0
reproduce (this is a W=1 build):
# https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=d38c8cfb057183f619dc8534030bb64b63f78043
git remote add linus https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
git fetch --no-tags linus master
git checkout d38c8cfb057183f619dc8534030bb64b63f78043
# 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 errors (new ones prefixed by >>):
>> drivers/pinctrl/intel/pinctrl-intel.c:210: error: Cannot parse enum!
vim +210 drivers/pinctrl/intel/pinctrl-intel.c
7981c0015af2632 Mika Westerberg 2015-03-30 192
1bd231538c21d1c Andy Shevchenko 2019-08-12 193 /**
1bd231538c21d1c Andy Shevchenko 2019-08-12 194 * enum - Locking variants of the pad configuration
1bd231538c21d1c Andy Shevchenko 2019-08-12 195 *
1bd231538c21d1c Andy Shevchenko 2019-08-12 196 * @PAD_UNLOCKED: pad is fully controlled by the configuration registers
1bd231538c21d1c Andy Shevchenko 2019-08-12 197 * @PAD_LOCKED: pad configuration registers, except TX state, are locked
1bd231538c21d1c Andy Shevchenko 2019-08-12 198 * @PAD_LOCKED_TX: pad configuration TX state is locked
1bd231538c21d1c Andy Shevchenko 2019-08-12 199 * @PAD_LOCKED_FULL: pad configuration registers are locked completely
1bd231538c21d1c Andy Shevchenko 2019-08-12 200 *
1bd231538c21d1c Andy Shevchenko 2019-08-12 201 * Locking is considered as read-only mode for corresponding registers and
1bd231538c21d1c Andy Shevchenko 2019-08-12 202 * their respective fields. That said, TX state bit is locked separately from
1bd231538c21d1c Andy Shevchenko 2019-08-12 203 * the main locking scheme.
1bd231538c21d1c Andy Shevchenko 2019-08-12 204 */
1bd231538c21d1c Andy Shevchenko 2019-08-12 205 enum {
1bd231538c21d1c Andy Shevchenko 2019-08-12 206 PAD_UNLOCKED = 0,
1bd231538c21d1c Andy Shevchenko 2019-08-12 207 PAD_LOCKED = 1,
1bd231538c21d1c Andy Shevchenko 2019-08-12 208 PAD_LOCKED_TX = 2,
1bd231538c21d1c Andy Shevchenko 2019-08-12 209 PAD_LOCKED_FULL = PAD_LOCKED | PAD_LOCKED_TX,
1bd231538c21d1c Andy Shevchenko 2019-08-12 @210 };
1bd231538c21d1c Andy Shevchenko 2019-08-12 211
:::::: The code at line 210 was first introduced by commit
:::::: 1bd231538c21d1cd691e71cbeeb4100fabc58068 pinctrl: intel: Allow to request locked pads
:::::: TO: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
:::::: CC: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
---
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: 50236 bytes --]
next reply other threads:[~2020-10-18 4:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-18 4:41 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-10-18 4:09 drivers/pinctrl/intel/pinctrl-intel.c:210: error: Cannot parse enum! kernel test robot
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=202010181218.snceHRO0-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox