From: Paul Gortmaker <paul.gortmaker@windriver.com>
To: Markus Pargmann <mpa@pengutronix.de>
Cc: Michael Grzeschik <mgr@pengutronix.de>,
Mark Brown <broonie@linaro.org>,
"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>
Subject: [next] ASoC fsl-ssi change breaks mpc85xx_defconfig build
Date: Wed, 11 Jun 2014 17:55:17 -0400 [thread overview]
Message-ID: <5398D045.3060906@windriver.com> (raw)
Hi Markus,
A bisection shows that this commit:
432481220101166a0b33dc6f951b38a8af3d281c is the first bad commit
commit 432481220101166a0b33dc6f951b38a8af3d281c
Author: Markus Pargmann <mpa@pengutronix.de>
Date: Tue May 27 10:24:25 2014 +0200
ASoC: fsl-ssi: Use regmap
found in linux-next causes the 85xx powerpc build to fail with:
sound/soc/fsl/fsl_dma.c: In function 'fsl_soc_dma_probe':
sound/soc/fsl/fsl_dma.c:926:34: error: invalid use of undefined type 'struct ccsr_ssi'
sound/soc/fsl/fsl_dma.c:927:34: error: invalid use of undefined type 'struct ccsr_ssi'
You can see the failure here as well:
http://kisskb.ellerman.id.au/kisskb/buildresult/11308076/
Paul.
next reply other threads:[~2014-06-11 21:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-11 21:55 Paul Gortmaker [this message]
2014-06-12 5:24 ` [next] ASoC fsl-ssi change breaks mpc85xx_defconfig build Markus Pargmann
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=5398D045.3060906@windriver.com \
--to=paul.gortmaker@windriver.com \
--cc=broonie@linaro.org \
--cc=linux-next@vger.kernel.org \
--cc=mgr@pengutronix.de \
--cc=mpa@pengutronix.de \
/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