alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: Liam Girdwood <lrg@ti.com>,
	alsa-devel@alsa-project.org, linux-omap@vger.kernel.org,
	Peter Ujfalusi <peter.ujfalusi@ti.com>
Subject: Re: [PATCH v2 0/2] ASoC: omap-mcpdm updates for 3.7
Date: Wed, 17 Oct 2012 12:55:26 -0700	[thread overview]
Message-ID: <20121017195525.GX15569@atomide.com> (raw)
In-Reply-To: <1349339236-3622-1-git-send-email-peter.ujfalusi@ti.com>

Hi Mark,

* Peter Ujfalusi <peter.ujfalusi@ti.com> [121004 01:27]:
> Hello Mark, Tony,
> 
> Change since v1:
> - Fixed the second patch to keep the omap_mcpdm_open_stream() - after a coffee
> 
> The mcpdm driver no longer needs to include any plat/*.h file, clearing the way
> for the single kernel image.
> 
> Regards,
> Peter
> ---
> Peter Ujfalusi (1):
>   ASoC: omap-mcpdm: Remove OMAP revision check
> 
> Tony Lindgren (1):
>   ASoC: Fix wrong include for McPDM
> 
>  sound/soc/omap/omap-mcpdm.c | 9 ++-------
>  1 file changed, 2 insertions(+), 7 deletions(-)

Is it OK for me to merge in your ASoC for-3.7 branch at commit
68214d99 (ASoC: omap-mcpdm: Remove OMAP revision check) also
into my omap cleanup branch for v3.8?

I need that to avoid compile errors with some of my test configs.

Regards,

Tony

  parent reply	other threads:[~2012-10-17 19:55 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-04  8:27 [PATCH v2 0/2] ASoC: omap-mcpdm updates for 3.7 Peter Ujfalusi
2012-10-04  8:27 ` [PATCH v2 1/2] ASoC: Fix wrong include for McPDM Peter Ujfalusi
2012-10-04 17:47   ` Mark Brown
2012-10-04 17:48   ` Mark Brown
2012-10-04 17:49   ` Mark Brown
2012-10-04  8:27 ` [PATCH v2 2/2] ASoC: omap-mcpdm: Remove OMAP revision check Peter Ujfalusi
2012-10-04 16:36   ` Tony Lindgren
2012-10-17 19:55 ` Tony Lindgren [this message]
2012-10-18 22:52   ` [PATCH v2 0/2] ASoC: omap-mcpdm updates for 3.7 Tony Lindgren
2012-10-19  1:27     ` Mark Brown
2012-10-19  2:23       ` Tony Lindgren

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=20121017195525.GX15569@atomide.com \
    --to=tony@atomide.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=linux-omap@vger.kernel.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 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).