All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Peter Ujfalusi <peter.ujfalusi@ti.com>
Cc: alsa-devel@alsa-project.org, Liam Girdwood <lrg@ti.com>
Subject: Re: [RESEND] ASoC: omap-abe-twl6040: Add device tree support
Date: Thu, 26 Jul 2012 10:52:39 +0100	[thread overview]
Message-ID: <20120726095238.GR3099@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <5010F73D.6020904@ti.com>


[-- Attachment #1.1: Type: text/plain, Size: 885 bytes --]

On Thu, Jul 26, 2012 at 10:52:29AM +0300, Peter Ujfalusi wrote:
> On 07/26/2012 12:48 AM, Mark Brown wrote:

> > Please just send the build fix with a followup adding the DT bindings
> > and then we can get the DT bindings in for 3.7.

> We do not have build breakage as of now since the DT bindings are not in.
> The build breakage happened on my local tree when I have rebased it on
> mainline yesterday. Stephen can not update the DT part of the omap-abe-twl6040
> when he did the snd_soc_dai_link cleanup, obviously.

Ah, sorry - I misread what you were saying and thought that there was a
build break in the current code.

> > Though obviously it's not even been compiled in mainline :/

> Sure it has not been compiled in mainline. It was/is compiled on top of
> mainline during my daily work.

Right, that was me thinking there was a build break with the currently
merged code.

[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]



  reply	other threads:[~2012-07-26 10:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-25 13:09 [RESEND] ASoC: omap-abe-twl6040: Add device tree support Peter Ujfalusi
2012-07-25 13:15 ` Mark Brown
2012-07-25 13:39   ` Peter Ujfalusi
2012-07-25 21:48     ` Mark Brown
2012-07-26  7:52       ` Peter Ujfalusi
2012-07-26  9:52         ` Mark Brown [this message]
2012-07-26 12:00 ` Mark Brown

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=20120726095238.GR3099@opensource.wolfsonmicro.com \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=lrg@ti.com \
    --cc=peter.ujfalusi@ti.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.