From: Jianqun <xjq@rock-chips.com>
To: Jim Davis <jim.epost@gmail.com>,
sfr@canb.auug.org.au, linux-next <linux-next@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
lgirdwood@gmail.com, broonie@kernel.org, perex@perex.cz,
tiwai@suse.de, grant.likely@linaro.org, robh+dt@kernel.org,
devicetree@vger.kernel.org, Heiko <heiko@sntech.de>
Subject: Re: randconfig build error with next-20140710, in sound/soc/rockchip/rockchip_i2s.c
Date: Fri, 11 Jul 2014 08:13:12 +0800 [thread overview]
Message-ID: <53BF2C18.10808@rock-chips.com> (raw)
In-Reply-To: <53BF2AB8.7050307@rock-chips.com>
Dear Heiko:
FYI
On 2014年07月11日 08:07, Jianqun wrote:
> Hi Heiko:
>
> Is it caused by the headfile ?
> #include <linux/module.h>
>
> Adviced by the maintainers, I tried not to include the headfile one by one, then to compile
> driver each time, I found that is success to compile it without module.h, of course
> I just compiled driver with command "ARCH=arm".
>
> Look up the codes, I found the functions like
> MODULE_DESCRIPTION
> will be defined as
> #define MODULE_DESCRIPTION(x) /* x */
> so the code in rockchip iis driver
> "MODULE_DESCRIPTION("ROCKCHIP IIS ASoC Interface") "
> will be defined as
> "ROCKCHIP IIS ASoC Interface"
> that should cause the error while robot to compile.
>
> Am I right ?
>
> If it is, do I need to make a new patch or just reply to the mail ? or how ...
>
>
> On 2014年07月10日 21:53, Jim Davis wrote:
>> Building with the attached random configuration file,
>>
>> sound/soc/rockchip/rockchip_i2s.c:526:20: error: expected declaration specifiers
>> or ‘...’ before string constant
>> MODULE_DESCRIPTION("ROCKCHIP IIS ASoC Interface");
>> ^
>> sound/soc/rockchip/rockchip_i2s.c:527:15: error: expected declaration specifiers
>> or ‘...’ before string constant
>> MODULE_AUTHOR("jianqun <jay.xu@rock-chips.com>");
>> ^
>> sound/soc/rockchip/rockchip_i2s.c:528:16: error: expected declaration specifiers
>> or ‘...’ before string constant
>> MODULE_LICENSE("GPL v2");
>> ^
>> sound/soc/rockchip/rockchip_i2s.c:529:14: error: expected declaration specifiers
>> or ‘...’ before string constant
>> MODULE_ALIAS("platform:" DRV_NAME);
>> ^
>> sound/soc/rockchip/rockchip_i2s.c:530:1: warning: data definition has no type or
>> storage class [enabled by default]
>> MODULE_DEVICE_TABLE(of, rockchip_i2s_match);
>> ^
>> sound/soc/rockchip/rockchip_i2s.c:530:1: error: type defaults to ‘int’
>> in declaration of ‘MODULE_DEVICE_TABLE’ [-Werror=implicit-int]
>> sound/soc/rockchip/rockchip_i2s.c:530:1: warning: parameter names (without types
>> ) in function declaration [enabled by default]
>> cc1: some warnings being treated as errors
>> make[3]: *** [sound/soc/rockchip/rockchip_i2s.o] Error 1
>>
>
--
-------------
许 剑 群 Jay
Rockchip Electronics Co.Ltd
****************************************************************************
*IMPORTANT NOTICE:*This email is from Fuzhou Rockchip Electronics Co.,
Ltd .The contents of this email and any attachments may contain
information that is privileged, confidential and/or exempt from
disclosure under applicable law and relevant NDA. If you are not the
intended recipient, you are hereby notified that any disclosure,
copying, distribution, or use of the information is STRICTLY PROHIBITED.
Please immediately contact the sender as soon as possible and destroy
the material in its entirety in any format. Thank you.
****************************************************************************
next prev parent reply other threads:[~2014-07-11 0:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-10 13:53 randconfig build error with next-20140710, in sound/soc/rockchip/rockchip_i2s.c Jim Davis
2014-07-11 0:07 ` Jianqun
2014-07-11 0:13 ` Jianqun [this message]
2014-07-11 0:32 ` Stephen Rothwell
2014-07-11 12:42 ` Mark Brown
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=53BF2C18.10808@rock-chips.com \
--to=xjq@rock-chips.com \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=grant.likely@linaro.org \
--cc=heiko@sntech.de \
--cc=jim.epost@gmail.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=perex@perex.cz \
--cc=robh+dt@kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=tiwai@suse.de \
/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