From: Jarkko Nikula <jarkko.nikula@bitmer.com>
To: Tomi Valkeinen <tomi.valkeinen@ti.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:42:27 +0300 [thread overview]
Message-ID: <4FC712D3.50103@bitmer.com> (raw)
In-Reply-To: <1338445869.1864.3.camel@lappyti>
On 05/31/2012 09:31 AM, Tomi Valkeinen wrote:
> 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.
>
You can still hit the build breakage by randconfig or if it's enabled by
default in the future and you start bisecting with that config old kernel.
>> 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
> =).
>
One simple - wait for next merge window. It's not that long. Only ~3
months and meanwhile one could keep boss/customer/wife/whatever
satisfied by carrying patches in own tree :-)
--
Jarkko
next prev parent reply other threads:[~2012-05-31 6:44 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
2012-05-31 6:42 ` Jarkko Nikula [this message]
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=4FC712D3.50103@bitmer.com \
--to=jarkko.nikula@bitmer.com \
--cc=jgq516@gmail.com \
--cc=linux-omap@vger.kernel.org \
--cc=ricardo.neri@ti.com \
--cc=tomi.valkeinen@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.