linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: Jarkko Nikula <jarkko.nikula@bitmer.com>
Cc: Ricardo Neri <ricardo.neri@ti.com>, Xiao Jiang <jgq516@gmail.com>,
	linux-omap@vger.kernel.org
Subject: Re: Compile err when enable CONFIG_SND_OMAP_SOC_OMAP_HDMI
Date: Thu, 31 May 2012 09:31:09 +0300	[thread overview]
Message-ID: <1338445869.1864.3.camel@lappyti> (raw)
In-Reply-To: <4FC704A4.2050806@bitmer.com>

[-- Attachment #1: Type: text/plain, Size: 1343 bytes --]

On Thu, 2012-05-31 at 08:41 +0300, Jarkko Nikula wrote:
> On 05/31/2012 02:35 AM, Ricardo Neri wrote:
> > Build breaks because there some patches [1] that are still missing in
> > Linus' tree. ASoC HDMI audio driver for OMAP[2] now uses the new DSS
> > audio functionality in [1], but ASoC patches were merged first. DSS
> > patches have been accepted and they are part of Tomi's pull request for
> > DSS for K3.5. Hopefully this will be fixed when v3.5-rc1 is out.
> > 
> Then there was an error already in the process if dependent sets didn't
> go together via the same merge or in next merge window. Remember each
> commit must compile alone.

They are going in in the same merge window. The asoc stuff has been
already merged, but the omapdss stuff hasn't.

It's true that there's a commit range where the asoc stuff doesn't
compile, and I agree that it's not good. But you need to explicitly
enable the HDMI ASOC support to get the error.

> It's quite boring to try to bisect over multiple kernel versions and
> where most of the time goes solving random unrelated build breakages.

How to get arm/arm/, omapdss, omapdrm and asoc driver changes in at the
same time? All go through various different trees and maintainers. I
haven't found a solution for this. If you have good ideas, please share
=).

 Tomi


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2012-05-31  6:31 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-30  7:14 Compile err when enable CONFIG_SND_OMAP_SOC_OMAP_HDMI Xiao Jiang
2012-05-30 23:35 ` Ricardo Neri
2012-05-31  4:27   ` Xiao Jiang
2012-06-05  1:24     ` Ricardo Neri
2012-06-05  4:15       ` Xiao Jiang
2012-06-05 15:51         ` Ricardo Neri
2012-06-06  3:01           ` Xiao Jiang
2012-05-31  5:41   ` Jarkko Nikula
2012-05-31  6:31     ` Tomi Valkeinen [this message]
2012-05-31  6:42       ` Jarkko Nikula
2012-05-31  7:00         ` Tomi Valkeinen
2012-05-31  8:23           ` Jarkko Nikula

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=1338445869.1864.3.camel@lappyti \
    --to=tomi.valkeinen@ti.com \
    --cc=jarkko.nikula@bitmer.com \
    --cc=jgq516@gmail.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=ricardo.neri@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).