From: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
To: kbuild test robot <lkp@intel.com>
Cc: kbuild-all@01.org, Ulf Hansson <ulf.hansson@linaro.org>,
linux-mmc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v1 3/3] mmc: pwrseq: convert to proper platform device
Date: Wed, 20 Jan 2016 14:12:55 +0000 [thread overview]
Message-ID: <569F95E7.4080305@linaro.org> (raw)
In-Reply-To: <201601202021.zTCtxQVb%fengguang.wu@intel.com>
Hi Ulf,
Just realized that this patch is totally broken when mmc support is
built as module. I will fix it and resend after v4.5-rc1
Thanks for kbuild test robot :-)
--srini
On 20/01/16 12:53, kbuild test robot wrote:
> Hi Srinivas,
>
> [auto build test ERROR on ulf.hansson-mmc/next]
> [also build test ERROR on next-20160120]
> [cannot apply to v4.4]
> [if your patch is applied to the wrong git tree, please drop us a note to help improving the system]
>
> url: https://github.com/0day-ci/linux/commits/Srinivas-Kandagatla/mmc-pwrseq-convert-to-proper-driver/20160120-185020
> base: https://git.linaro.org/people/ulf.hansson/mmc next
> config: openrisc-allmodconfig (attached as .config)
> reproduce:
> wget https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross -O ~/bin/make.cross
> chmod +x ~/bin/make.cross
> # save the attached .config to linux build tree
> make.cross ARCH=openrisc
>
> All error/warnings (new ones prefixed by >>):
>
>>> drivers/mmc/core/pwrseq_emmc.c:120:1: warning: data definition has no type or storage class
>>> drivers/mmc/core/pwrseq_emmc.c:120:1: error: type defaults to 'int' in declaration of 'device_initcall'
> drivers/mmc/core/pwrseq_emmc.c:120:1: warning: parameter names (without types) in function declaration
> drivers/mmc/core/pwrseq_emmc.c:120:1: warning: 'mmc_pwrseq_emmc_driver_init' defined but not used
>
> vim +120 drivers/mmc/core/pwrseq_emmc.c
>
> 114 .driver = {
> 115 .name = "pwrseq_emmc",
> 116 .of_match_table = mmc_pwrseq_emmc_of_match,
> 117 },
> 118 };
> 119
> > 120 builtin_platform_driver(mmc_pwrseq_emmc_driver);
>
> ---
> 0-DAY kernel test infrastructure Open Source Technology Center
> https://lists.01.org/pipermail/kbuild-all Intel Corporation
>
WARNING: multiple messages have this Message-ID (diff)
From: srinivas.kandagatla@linaro.org (Srinivas Kandagatla)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v1 3/3] mmc: pwrseq: convert to proper platform device
Date: Wed, 20 Jan 2016 14:12:55 +0000 [thread overview]
Message-ID: <569F95E7.4080305@linaro.org> (raw)
In-Reply-To: <201601202021.zTCtxQVb%fengguang.wu@intel.com>
Hi Ulf,
Just realized that this patch is totally broken when mmc support is
built as module. I will fix it and resend after v4.5-rc1
Thanks for kbuild test robot :-)
--srini
On 20/01/16 12:53, kbuild test robot wrote:
> Hi Srinivas,
>
> [auto build test ERROR on ulf.hansson-mmc/next]
> [also build test ERROR on next-20160120]
> [cannot apply to v4.4]
> [if your patch is applied to the wrong git tree, please drop us a note to help improving the system]
>
> url: https://github.com/0day-ci/linux/commits/Srinivas-Kandagatla/mmc-pwrseq-convert-to-proper-driver/20160120-185020
> base: https://git.linaro.org/people/ulf.hansson/mmc next
> config: openrisc-allmodconfig (attached as .config)
> reproduce:
> wget https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross -O ~/bin/make.cross
> chmod +x ~/bin/make.cross
> # save the attached .config to linux build tree
> make.cross ARCH=openrisc
>
> All error/warnings (new ones prefixed by >>):
>
>>> drivers/mmc/core/pwrseq_emmc.c:120:1: warning: data definition has no type or storage class
>>> drivers/mmc/core/pwrseq_emmc.c:120:1: error: type defaults to 'int' in declaration of 'device_initcall'
> drivers/mmc/core/pwrseq_emmc.c:120:1: warning: parameter names (without types) in function declaration
> drivers/mmc/core/pwrseq_emmc.c:120:1: warning: 'mmc_pwrseq_emmc_driver_init' defined but not used
>
> vim +120 drivers/mmc/core/pwrseq_emmc.c
>
> 114 .driver = {
> 115 .name = "pwrseq_emmc",
> 116 .of_match_table = mmc_pwrseq_emmc_of_match,
> 117 },
> 118 };
> 119
> > 120 builtin_platform_driver(mmc_pwrseq_emmc_driver);
>
> ---
> 0-DAY kernel test infrastructure Open Source Technology Center
> https://lists.01.org/pipermail/kbuild-all Intel Corporation
>
next prev parent reply other threads:[~2016-01-20 14:13 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-20 10:45 [PATCH v1 0/3] mmc: pwrseq: convert to proper driver Srinivas Kandagatla
2016-01-20 10:45 ` Srinivas Kandagatla
2016-01-20 10:46 ` [PATCH v1 1/3] mmc: pwrseq_simple: add to_pwrseq_simple() macro Srinivas Kandagatla
2016-01-20 10:46 ` Srinivas Kandagatla
2016-01-20 10:46 ` [PATCH v1 2/3] mmc: pwrseq_emmc: add to_pwrseq_emmc() macro Srinivas Kandagatla
2016-01-20 10:46 ` Srinivas Kandagatla
2016-01-20 10:46 ` [PATCH v1 3/3] mmc: pwrseq: convert to proper platform device Srinivas Kandagatla
2016-01-20 10:46 ` Srinivas Kandagatla
2016-01-20 12:53 ` kbuild test robot
2016-01-20 12:53 ` kbuild test robot
2016-01-20 12:53 ` kbuild test robot
2016-01-20 14:12 ` Srinivas Kandagatla [this message]
2016-01-20 14:12 ` Srinivas Kandagatla
2016-01-20 16:04 ` kbuild test robot
2016-01-20 16:04 ` kbuild test robot
2016-01-20 16:04 ` kbuild 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=569F95E7.4080305@linaro.org \
--to=srinivas.kandagatla@linaro.org \
--cc=kbuild-all@01.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=lkp@intel.com \
--cc=ulf.hansson@linaro.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.