From: Peter Ujfalusi <peter.ujfalusi@ti.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: Brian Austin <brian.austin@cirrus.com>,
Tony Lindgren <tony@atomide.com>,
alsa-devel@alsa-project.org, linux-next@vger.kernel.org,
linux-omap@vger.kernel.org, Liam Girdwood <lrg@ti.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] ARM: OMAP2+: twl-common: Fix compile time error when omap-twl4030 audio is not enabled
Date: Thu, 23 Aug 2012 15:25:45 +0300 [thread overview]
Message-ID: <50362149.6020107@ti.com> (raw)
In-Reply-To: <20120823112204.GY7995@opensource.wolfsonmicro.com>
On 08/23/2012 02:22 PM, Mark Brown wrote:
> Which branch needs this?
for-3.7, for-next and topic/omap needs this patch.
--
Péter
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
WARNING: multiple messages have this Message-ID (diff)
From: peter.ujfalusi@ti.com (Peter Ujfalusi)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: OMAP2+: twl-common: Fix compile time error when omap-twl4030 audio is not enabled
Date: Thu, 23 Aug 2012 15:25:45 +0300 [thread overview]
Message-ID: <50362149.6020107@ti.com> (raw)
In-Reply-To: <20120823112204.GY7995@opensource.wolfsonmicro.com>
On 08/23/2012 02:22 PM, Mark Brown wrote:
> Which branch needs this?
for-3.7, for-next and topic/omap needs this patch.
--
P?ter
next prev parent reply other threads:[~2012-08-23 12:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-23 6:35 [PATCH] ARM: OMAP2+: twl-common: Fix compile time error when omap-twl4030 audio is not enabled Peter Ujfalusi
2012-08-23 6:35 ` Peter Ujfalusi
2012-08-23 11:22 ` Mark Brown
2012-08-23 11:22 ` Mark Brown
2012-08-23 12:14 ` Austin, Brian
2012-08-23 12:14 ` Austin, Brian
2012-08-23 12:25 ` Peter Ujfalusi [this message]
2012-08-23 12:25 ` Peter Ujfalusi
2012-08-23 14:39 ` Mark Brown
2012-08-23 14:39 ` 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=50362149.6020107@ti.com \
--to=peter.ujfalusi@ti.com \
--cc=alsa-devel@alsa-project.org \
--cc=brian.austin@cirrus.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=lrg@ti.com \
--cc=tony@atomide.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.