From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [sailus-media:fixes 2/2] drivers/media/i2c/max9271.c:343:16: error: expected declaration specifiers or '...' before string constant
Date: Wed, 10 Feb 2021 20:44:14 +0800 [thread overview]
Message-ID: <202102102009.rwFUZLdm-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1348 bytes --]
tree: git://linuxtv.org/sailus/media_tree.git fixes
head: 4cfc8619462b4a3a1b2fd09f0321486e3143f5fc
commit: 4cfc8619462b4a3a1b2fd09f0321486e3143f5fc [2/2] media: max9271: Add missing MODULE_LICENSE
config: mips-randconfig-r016-20210209 (attached as .config)
compiler: mips64-linux-gcc (GCC) 9.3.0
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
git remote add sailus-media git://linuxtv.org/sailus/media_tree.git
git fetch --no-tags sailus-media fixes
git checkout 4cfc8619462b4a3a1b2fd09f0321486e3143f5fc
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=mips
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/media/i2c/max9271.c:343:16: error: expected declaration specifiers or '...' before string constant
343 | MODULE_LICENSE("GPL");
| ^~~~~
vim +343 drivers/media/i2c/max9271.c
342
> 343 MODULE_LICENSE("GPL");
---
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: 36505 bytes --]
reply other threads:[~2021-02-10 12:44 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=202102102009.rwFUZLdm-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@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.