From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Ulf Hansson <ulf.hansson@linaro•org>
Cc: linux-next@vger•kernel.org, linux-kernel@vger•kernel.org,
Sonny Rao <sonnyrao@chromium•org>
Subject: Re: linux-next: build failure after merge of the mmc-uh tree
Date: Fri, 8 Aug 2014 13:25:10 +1000 [thread overview]
Message-ID: <20140808132510.68e8ae66@canb.auug.org.au> (raw)
In-Reply-To: <20140728144608.7d9ac736@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 817 bytes --]
Hi all,
On Mon, 28 Jul 2014 14:46:08 +1000 Stephen Rothwell <sfr@canb•auug.org.au> wrote:
>
> After merging the mmc-uh tree, today's linux-next build (arm
> multi_v7_defconfig) failed like this:
>
> drivers/mmc/host/dw_mmc.c: In function 'dw_mci_reset':
> drivers/mmc/host/dw_mmc.c:2262:3: error: implicit declaration of function 'dw_mci_idmac_reset' [-Werror=implicit-function-declaration]
> dw_mci_idmac_reset(host);
> ^
>
> Caused by commit 25f7dadbd982 ("mmc: dw_mmc: change to use recommended
> reset procedure").
>
> I have used the mmc-uh tree from next-20140725 for today.
Ping. We are nearly half way through the merge window and there has
been a patch posted for this, but the tree is still broken ...
--
Cheers,
Stephen Rothwell sfr@canb•auug.org.au
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2014-08-08 3:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-28 4:46 linux-next: build failure after merge of the mmc-uh tree Stephen Rothwell
2014-07-28 17:58 ` Sonny Rao
2014-08-04 13:44 ` Ulf Hansson
2014-08-05 1:19 ` [PATCH] mmc: dw_mmc: change to use recommended reset procedure Sonny Rao
2014-08-07 8:40 ` Jaehoon Chung
2014-08-11 7:55 ` Ulf Hansson
2014-08-08 3:25 ` Stephen Rothwell [this message]
2014-08-11 7:54 ` linux-next: build failure after merge of the mmc-uh tree Ulf Hansson
-- strict thread matches above, loose matches on Subject: below --
2015-08-26 2:04 Stephen Rothwell
2015-12-31 3:53 Stephen Rothwell
2016-01-05 16:30 ` Thierry Reding
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=20140808132510.68e8ae66@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sonnyrao@chromium$(echo .)org \
--cc=ulf.hansson@linaro$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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