From: Peter Ujfalusi <peter.ujfalusi@ti.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: Tony Lindgren <tony@atomide.com>, Liam Girdwood <lrg@ti.com>,
Jarkko Nikula <jarkko.nikula@bitmer.com>,
alsa-devel@alsa-project.org, linux-omap@vger.kernel.org,
Janusz Krzysztofik <jkrzyszt@tis.icnet.pl>,
Grazvydas Ignotas <notasas@gmail.com>
Subject: Re: [PATCH v2 00/10] OMAP/ASoC: Move and merge McBSP driver under ASoC
Date: Fri, 02 Mar 2012 16:37:17 +0200 [thread overview]
Message-ID: <4F50DB1D.1090007@ti.com> (raw)
In-Reply-To: <20120228104925.GA3683@opensource.wolfsonmicro.com>
Hi Mark,
On 02/28/2012 12:49 PM, Mark Brown wrote:
> On Tue, Feb 28, 2012 at 09:40:10AM +0200, Peter Ujfalusi wrote:
>
>> NOTE: this series has been generated agains Takashi's topic/asoc branch merged
>> with Mark's for-next branch since this series depends on changes in Marks'
>> branch, but not yet pulled by Takashi (snd_soc_add_dai_controls implementation
>> from Liam).
>
> Never base *anything* off my for-next branch, it gets rebuilt regularly.
Sorry it was my mistake. I have merged your for-3.4 branch with
Takashi's topic/asoc to be able test the v2 series which dropped my
version of snd_soc_add_dai_controls()
Sometimes I use your for-next branch, but I'm not building on top of it
since I have also noticed that it got rebuilt occasionally.
--
Péter
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2012-03-02 14:37 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-28 7:40 [PATCH v2 00/10] OMAP/ASoC: Move and merge McBSP driver under ASoC Peter Ujfalusi
2012-02-28 7:40 ` [PATCH v2 01/10] ARM: OMAP: mcbsp: Convert core driver to proper platform driver Peter Ujfalusi
2012-02-28 19:32 ` Jarkko Nikula
2012-02-28 7:40 ` [PATCH v2 02/10] OMAP: mcbsp: Move core driver under sound/soc/omap Peter Ujfalusi
2012-02-28 7:40 ` [PATCH v2 03/10] ASoC: OMAP: McBSP: Consolidate plat/mcbsp.h content Peter Ujfalusi
2012-02-29 23:30 ` Mark Brown
2012-02-28 7:40 ` [PATCH v2 04/10] ASoC: omap-mcbsp: Create a single driver for McBSP Peter Ujfalusi
2012-02-29 23:31 ` Mark Brown
2012-02-28 7:40 ` [PATCH v2 05/10] ARM: OMAP: Do not register omap-mcbsp-dai device Peter Ujfalusi
2012-02-28 7:40 ` [PATCH v2 06/10] ASoC: OMAP: mcbsp.h: Clean up bit definitions Peter Ujfalusi
2012-02-28 7:40 ` [PATCH v2 07/10] ASoC: OMAP McBSP: Remove redundant accessors Peter Ujfalusi
2012-02-28 7:40 ` [PATCH v2 08/10] ASoC: omap-mcbsp: Cleanup of module probe/remove code Peter Ujfalusi
2012-02-29 23:33 ` Mark Brown
2012-02-28 7:40 ` [PATCH v2 09/10] ASoC: omap-mcbsp: Merge the omap_mcbsp_data into omap_mcbsp structure Peter Ujfalusi
2012-02-29 23:33 ` Mark Brown
2012-02-28 7:40 ` [PATCH v2 10/10] ASoC: omap-mcbsp: Simplify DMA configuration Peter Ujfalusi
2012-02-29 23:34 ` Mark Brown
2012-02-28 10:49 ` [PATCH v2 00/10] OMAP/ASoC: Move and merge McBSP driver under ASoC Mark Brown
2012-03-02 14:37 ` Peter Ujfalusi [this message]
2012-02-28 19:32 ` 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=4F50DB1D.1090007@ti.com \
--to=peter.ujfalusi@ti.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=jarkko.nikula@bitmer.com \
--cc=jkrzyszt@tis.icnet.pl \
--cc=linux-omap@vger.kernel.org \
--cc=lrg@ti.com \
--cc=notasas@gmail.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.