From: kbuild test robot <fengguang.wu@intel.com>
To: Seungwon Jeon <tgih.jun@samsung.com>
Cc: kbuild-all@01.org, Ulf Hansson <ulf.hansson@linaro.org>,
Alim Akhtar <alim.akhtar@samsung.com>,
Jaehoon Chung <jh80.chung@samsung.com>,
Chris Ball <chris@printf.net>, Kukjin Kim <kgene@kernel.org>,
linux-mmc@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [ulf.hansson-mmc:next 1/17] drivers/mmc/host/dw_mmc-exynos.c:480:5: sparse: symbol 'dw_mci_exynos_prepare_hs400_tuning' was not declared. Should it be static?
Date: Thu, 5 Mar 2015 18:02:54 +0800 [thread overview]
Message-ID: <201503051843.EsoMldBU%fengguang.wu@intel.com> (raw)
tree: https://git.linaro.org/people/ulf.hansson/mmc next
head: cc92508d8a444000ec259debaf7603faf77540de
commit: 880e5e640a1f39802da76d9570bed2d8456f302a [1/17] mmc: dw_mmc: exynos: Support eMMC's HS400 mode
reproduce:
# apt-get install sparse
git checkout 880e5e640a1f39802da76d9570bed2d8456f302a
make ARCH=x86_64 allmodconfig
make C=1 CF=-D__CHECK_ENDIAN__
sparse warnings: (new ones prefixed by >>)
>> drivers/mmc/host/dw_mmc-exynos.c:480:5: sparse: symbol 'dw_mci_exynos_prepare_hs400_tuning' was not declared. Should it be static?
--
>> drivers/mmc/host/dw_mmc.c:1327:5: sparse: symbol 'dw_mci_prepare_hs400_tuning' was not declared. Should it be static?
drivers/mmc/host/dw_mmc.c:2913:1: sparse: symbol '__UNIQUE_ID_author__COUNTER__' has multiple initializers (originally initialized at drivers/mmc/host/dw_mmc.c:2912)
Please review and possibly fold the followup patch.
---
0-DAY kernel test infrastructure Open Source Technology Center
http://lists.01.org/mailman/listinfo/kbuild Intel Corporation
next reply other threads:[~2015-03-05 10:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-05 10:02 kbuild test robot [this message]
2015-03-05 10:02 ` [PATCH ulf.hansson-mmc] mmc: dw_mmc: exynos: dw_mci_exynos_prepare_hs400_tuning() can be static kbuild test robot
2015-03-05 10:13 ` Jaehoon Chung
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=201503051843.EsoMldBU%fengguang.wu@intel.com \
--to=fengguang.wu@intel.com \
--cc=alim.akhtar@samsung.com \
--cc=chris@printf.net \
--cc=jh80.chung@samsung.com \
--cc=kbuild-all@01.org \
--cc=kgene@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=tgih.jun@samsung.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®