public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Simon Horman <horms@verge.net.au>
To: Mark Brown <broonie@kernel.org>
Cc: Arnd Bergmann <arnd@arndb.de>,
	Wolfram Sang <wsa+renesas@sang-engineering.com>,
	Ulf Hansson <ulf.hansson@linaro.org>,
	linaro-kernel@lists.linaro.org, linux-next@vger.kernel.org,
	linux-arm-kernel@lists.infreadead.org,
	kernel-build-reports@lists.linaro.org
Subject: Re: next-20170522 build: 2 failures 7 warnings (next-20170522)
Date: Tue, 23 May 2017 07:28:28 +0200	[thread overview]
Message-ID: <20170523052828.GB25840@verge.net.au> (raw)
In-Reply-To: <20170522150600.ewzu55g4ootbt7tm@sirena.org.uk>

On Mon, May 22, 2017 at 04:06:00PM +0100, Mark Brown wrote:
> On Mon, May 22, 2017 at 01:39:11PM +0100, Build bot for Mark Brown wrote:
> 
> Today's -next fails to build both arm and arm64 allmodconfig due to:
> 
> > 	arm64-allmodconfig
> > ERROR: "renesas_sdhi_remove" [drivers/mmc/host/renesas_sdhi_sys_dmac.ko] undefined!
> > ERROR: "renesas_sdhi_probe" [drivers/mmc/host/renesas_sdhi_sys_dmac.ko] undefined!
> 
> > 	arm-allmodconfig
> > ERROR: "renesas_sdhi_remove" [drivers/mmc/host/renesas_sdhi_sys_dmac.ko] undefined!
> > ERROR: "renesas_sdhi_probe" [drivers/mmc/host/renesas_sdhi_sys_dmac.ko] undefined!
> 
> caused by the recent refactoring which created renesas_sdhi_core.c -
> those symbols aren't exported.

Sorry about that. I believe Arnd (CCed) posted a patch to resolve
this problem which Ulf has applied.

The patch is "[PATCH] mmc: renesas-sdhi: export renesas_sdhi_probe"

      reply	other threads:[~2017-05-23  5:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-22 12:39 next-20170522 build: 2 failures 7 warnings (next-20170522) Build bot for Mark Brown
2017-05-22 15:06 ` Mark Brown
2017-05-23  5:28   ` Simon Horman [this message]

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=20170523052828.GB25840@verge.net.au \
    --to=horms@verge.net.au \
    --cc=arnd@arndb.de \
    --cc=broonie@kernel.org \
    --cc=kernel-build-reports@lists.linaro.org \
    --cc=linaro-kernel@lists.linaro.org \
    --cc=linux-arm-kernel@lists.infreadead.org \
    --cc=linux-next@vger.kernel.org \
    --cc=ulf.hansson@linaro.org \
    --cc=wsa+renesas@sang-engineering.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