linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Peter Robinson <pbrobinson@gmail.com>
Cc: kbuild-all@01.org, Lee Jones <lee.jones@linaro.org>,
	patches@opensource.wolfsonmicro.com,
	linux-kernel@vger.kernel.org,
	Mark Brown <broonie@opensource.wolfsonmicro.com>,
	Peter Robinson <pbrobinson@gmail.com>,
	stable@vger.kernel.org
Subject: Re: [PATCH] mfd: wm8994: Add module description/author/license information
Date: Sat, 7 Nov 2015 21:55:54 +0800	[thread overview]
Message-ID: <201511072142.rolfTlHL%fengguang.wu@intel.com> (raw)
In-Reply-To: <1446899331-7754-1-git-send-email-pbrobinson@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1843 bytes --]

Hi Peter,

[auto build test ERROR on: ljones-mfd/for-mfd-next]
[also build test ERROR on: v4.3 next-20151106]

url:    https://github.com/0day-ci/linux/commits/Peter-Robinson/mfd-wm8994-Add-module-description-author-license-information/20151107-203151
base:   https://git.kernel.org/pub/scm/linux/kernel/git/lee/mfd.git for-mfd-next
config: x86_64-randconfig-i0-11072104 (attached as .config)
reproduce:
        # save the attached .config to linux build tree
        make ARCH=x86_64 

All errors (new ones prefixed by >>):

>> drivers/mfd/wm8994-regmap.c:1293:20: error: expected declaration specifiers or '...' before string constant
    MODULE_DESCRIPTION("WM8994 Register mapping data");
                       ^
   drivers/mfd/wm8994-regmap.c:1294:15: error: expected declaration specifiers or '...' before string constant
    MODULE_AUTHOR("Mark Brown <broonie@opensource.wolfsonmicro.com>");
                  ^
   drivers/mfd/wm8994-regmap.c:1295:16: error: expected declaration specifiers or '...' before string constant
    MODULE_LICENSE("GPL v2");
                   ^
   drivers/mfd/wm8994-regmap.c:1296:14: error: expected declaration specifiers or '...' before string constant
    MODULE_ALIAS("platform:wm8994-regmap");
                 ^

vim +1293 drivers/mfd/wm8994-regmap.c

  1287	struct regmap_config wm8994_base_regmap_config = {
  1288		.reg_bits = 16,
  1289		.val_bits = 16,
  1290	};
  1291	EXPORT_SYMBOL(wm8994_base_regmap_config);
  1292	
> 1293	MODULE_DESCRIPTION("WM8994 Register mapping data");
  1294	MODULE_AUTHOR("Mark Brown <broonie@opensource.wolfsonmicro.com>");
  1295	MODULE_LICENSE("GPL v2");
  1296	MODULE_ALIAS("platform:wm8994-regmap");

---
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: 18321 bytes --]

  reply	other threads:[~2015-11-07 13:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-07 12:28 [PATCH] mfd: wm8994: Add module description/author/license information Peter Robinson
2015-11-07 13:55 ` kbuild test robot [this message]
2015-11-07 16:25 v2 mfd: wm8994: Add module description/author/license Peter Robinson
2015-11-07 16:25 ` [PATCH] mfd: wm8994: Add module description/author/license information Peter Robinson
2015-11-10 10:10   ` Charles Keepax

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=201511072142.rolfTlHL%fengguang.wu@intel.com \
    --to=lkp@intel.com \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=kbuild-all@01.org \
    --cc=lee.jones@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=patches@opensource.wolfsonmicro.com \
    --cc=pbrobinson@gmail.com \
    --cc=stable@vger.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;
as well as URLs for NNTP newsgroup(s).