From: kbuild test robot <fengguang.wu@intel.com>
To: unlisted-recipients:; (no To-header on input)
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org,
tipbuild@zytor.com, Ingo Molnar <mingo@kernel.org>,
Paul Gortmaker <paul.gortmaker@windriver.com>
Subject: [tip:x86/headers 6/9] arch/x86/platform/ts5500/ts5500.c:349:16: error: expected declaration specifiers or '...' before string constant
Date: Sat, 16 Jul 2016 03:53:45 +0800 [thread overview]
Message-ID: <201607160331.PgBe9MF1%fengguang.wu@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2311 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86/headers
head: eb008eb6f8b689853d6e9f4ae3ff56ea734e4319
commit: cc3ae7b0af27118994c1e491382b253be3b762bf [6/9] x86/platform: Audit and remove any unnecessary uses of module.h
config: i386-randconfig-c0-07160258 (attached as .config)
compiler: gcc-6 (Debian 6.1.1-1) 6.1.1 20160430
reproduce:
git checkout cc3ae7b0af27118994c1e491382b253be3b762bf
# save the attached .config to linux build tree
make ARCH=i386
All errors (new ones prefixed by >>):
>> arch/x86/platform/ts5500/ts5500.c:349:16: error: expected declaration specifiers or '...' before string constant
MODULE_LICENSE("GPL");
^~~~~
arch/x86/platform/ts5500/ts5500.c:350:15: error: expected declaration specifiers or '...' before string constant
MODULE_AUTHOR("Savoir-faire Linux Inc. <kernel@savoirfairelinux.com>");
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
arch/x86/platform/ts5500/ts5500.c:351:20: error: expected declaration specifiers or '...' before string constant
MODULE_DESCRIPTION("Technologic Systems TS-5500 platform driver");
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
vim +349 arch/x86/platform/ts5500/ts5500.c
7d029125 Vivien Didelot 2013-01-04 343 error:
7d029125 Vivien Didelot 2013-01-04 344 platform_device_unregister(pdev);
7d029125 Vivien Didelot 2013-01-04 345 return err;
7d029125 Vivien Didelot 2013-01-04 346 }
7d029125 Vivien Didelot 2013-01-04 347 device_initcall(ts5500_init);
7d029125 Vivien Didelot 2013-01-04 348
7d029125 Vivien Didelot 2013-01-04 @349 MODULE_LICENSE("GPL");
7d029125 Vivien Didelot 2013-01-04 350 MODULE_AUTHOR("Savoir-faire Linux Inc. <kernel@savoirfairelinux.com>");
7d029125 Vivien Didelot 2013-01-04 351 MODULE_DESCRIPTION("Technologic Systems TS-5500 platform driver");
:::::: The code at line 349 was first introduced by commit
:::::: 7d0291256ca99cbb6124f63228003329e7a64b21 x86: Add TS-5500 platform support
:::::: TO: Vivien Didelot <vivien.didelot@savoirfairelinux.com>
:::::: CC: Ingo Molnar <mingo@kernel.org>
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/octet-stream, Size: 26700 bytes --]
next reply other threads:[~2016-07-15 19:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-15 19:53 kbuild test robot [this message]
2016-07-15 23:53 ` [tip:x86/headers 6/9] arch/x86/platform/ts5500/ts5500.c:349:16: error: expected declaration specifiers or '...' before string constant Paul Gortmaker
2016-07-16 20:52 ` [tip:x86/headers] x86/platform: Delete extraneous MODULE_* tags fromm ts5500 tip-bot for Paul Gortmaker
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=201607160331.PgBe9MF1%fengguang.wu@intel.com \
--to=fengguang.wu@intel.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=paul.gortmaker@windriver.com \
--cc=tipbuild@zytor.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;
as well as URLs for NNTP newsgroup(s).