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,
Srinivas Kandagatla <srinivas.kandagatla@linaro•org>
Subject: linux-next: build failure after merge of the mmc-uh tree
Date: Wed, 26 Aug 2015 12:04:35 +1000 [thread overview]
Message-ID: <20150826120435.27ed1e89@canb.auug.org.au> (raw)
Hi Ulf,
After merging the mmc-uh tree, today's linux-next build (x86_64
allmodconfig) failed like this:
ERROR: "pinctrl_bind_pins" [drivers/mmc/core/mmc_core.ko] undefined!
Caused by commit
175172f6367f ("mmc: pwrseq: bind pinctrl pins before using the gpios")
I have used te mmc-uh tree from next-20150825 for today.
--
Cheers,
Stephen Rothwell sfr@canb•auug.org.au
next reply other threads:[~2015-08-26 2:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-26 2:04 Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-12-31 3:53 linux-next: build failure after merge of the mmc-uh tree Stephen Rothwell
2016-01-05 16:30 ` Thierry Reding
2014-07-28 4:46 Stephen Rothwell
2014-07-28 17:58 ` Sonny Rao
2014-08-04 13:44 ` Ulf Hansson
2014-08-08 3:25 ` Stephen Rothwell
2014-08-11 7:54 ` Ulf Hansson
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=20150826120435.27ed1e89@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=srinivas.kandagatla@linaro$(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