From: Markus Pargmann <mpa@pengutronix.de>
To: Paul Gortmaker <paul.gortmaker@windriver.com>
Cc: Michael Grzeschik <mgr@pengutronix.de>,
Mark Brown <broonie@linaro.org>,
"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
Guenter Roeck <linux@roeck-us.net>
Subject: Re: [next] ASoC fsl-ssi change breaks mpc85xx_defconfig build
Date: Thu, 12 Jun 2014 07:24:11 +0200 [thread overview]
Message-ID: <20140612052411.GA24404@pengutronix.de> (raw)
In-Reply-To: <5398D045.3060906@windriver.com>
[-- Attachment #1: Type: text/plain, Size: 1202 bytes --]
Hi Paul,
On Wed, Jun 11, 2014 at 05:55:17PM -0400, Paul Gortmaker wrote:
> 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'
Guenter also noticed this build failure and sent a patch which was
applied by Mark yesterday. [1]
Thanks,
Markus
[1] http://thread.gmane.org/gmane.linux.ports.ppc.embedded/70977
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2014-06-12 5:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-11 21:55 [next] ASoC fsl-ssi change breaks mpc85xx_defconfig build Paul Gortmaker
2014-06-12 5:24 ` Markus Pargmann [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=20140612052411.GA24404@pengutronix.de \
--to=mpa@pengutronix.de \
--cc=broonie@linaro.org \
--cc=linux-next@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=mgr@pengutronix.de \
--cc=paul.gortmaker@windriver.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