From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Tony Lindgren <tony@atomide.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: Fri, 19 Oct 2012 02:27:51 +0100 [thread overview]
Message-ID: <20121019012751.GA2353@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <20121018225237.GJ30550@atomide.com>
On Thu, Oct 18, 2012 at 03:52:37PM -0700, Tony Lindgren wrote:
> * Tony Lindgren <tony@atomide.com> [121017 13:01]:
> > 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.
> Never mind, that seems to be merged now.
That's easy :) Sorry about the delay, OMAP stuff tends to get delayed
as there's so many large patch serieses posted in multiple versions that
I get CCed on I tend to batch process it.
FWIW signed tags are fair game for merging without asking (in this case
asoc-3.7) but please don't merge any of my branches directly, I'll make
a tag.
next prev parent reply other threads:[~2012-10-19 1:27 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 ` [PATCH v2 0/2] ASoC: omap-mcpdm updates for 3.7 Tony Lindgren
2012-10-18 22:52 ` Tony Lindgren
2012-10-19 1:27 ` Mark Brown [this message]
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=20121019012751.GA2353@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=linux-omap@vger.kernel.org \
--cc=lrg@ti.com \
--cc=peter.ujfalusi@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.