From: Chris Ball <cjb@laptop.org>
To: kbuild test robot <fengguang.wu@intel.com>
Cc: Seungwon Jeon <tgih.jun@samsung.com>, linux-mmc@vger.kernel.org
Subject: Re: [mmc:mmc-next 17/28] sdhci-pltfm.c:(.text+0x80): multiple definition of `sdhci_runtime_pm_get'
Date: Wed, 07 Nov 2012 15:43:05 -0500 [thread overview]
Message-ID: <87ip9h6t5y.fsf@octavius.laptop.org> (raw)
In-Reply-To: <509ac6c4.cYfNNpMXVvvrRu6C%fengguang.wu@intel.com> (kbuild test robot's message of "Thu, 08 Nov 2012 04:38:28 +0800")
Hi,
On Wed, Nov 07 2012, kbuild test robot wrote:
> tree: git://git.kernel.org/pub/scm/linux/kernel/git/cjb/mmc.git mmc-next
> head: a6a567a4c25762e36228d2d0c8c1859085132e15
> commit: 90ba86ed414e8ab4d84fe3342f10948c607efa7a [17/28] mmc:
> sdhci-s3c: ensure non-transaction of bus before clk_disable
> config: i386-randconfig-b646 (attached as .config)
>
> All error/warnings:
>
> drivers/mmc/host/sdhci-pltfm.o: In function `sdhci_runtime_pm_get':
> sdhci-pltfm.c:(.text+0x80): multiple definition of `sdhci_runtime_pm_get'
> drivers/mmc/host/sdhci.o:sdhci.c:(.text+0x7550): first defined here
> drivers/mmc/host/sdhci-pltfm.o: In function `sdhci_runtime_pm_put':
> sdhci-pltfm.c:(.text+0xa0): multiple definition of `sdhci_runtime_pm_put'
> drivers/mmc/host/sdhci.o:sdhci.c:(.text+0x7570): first defined here
Yay for buildbots. Seungwon, I've dropped this patch from mmc-next now,
please investigate and fix.
(Wu, are you sure that this is the correct config? It's i386 without
MMC_SDHCI_S3C=y, and MMC_SDHCI_S3C depends on PLAT_SAMSUNG/ARM.)
Thanks,
- Chris.
--
Chris Ball <cjb@laptop.org> <http://printf.net/>
One Laptop Per Child
next prev parent reply other threads:[~2012-11-07 20:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-07 20:38 [mmc:mmc-next 17/28] sdhci-pltfm.c:(.text+0x80): multiple definition of `sdhci_runtime_pm_get' kbuild test robot
2012-11-07 20:43 ` Chris Ball [this message]
2012-11-08 12:08 ` Fengguang Wu
2012-11-08 12:21 ` Chris Ball
2012-11-09 10:24 ` Seungwon Jeon
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=87ip9h6t5y.fsf@octavius.laptop.org \
--to=cjb@laptop.org \
--cc=fengguang.wu@intel.com \
--cc=linux-mmc@vger.kernel.org \
--cc=tgih.jun@samsung.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