From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org, Liam Girdwood <lrg@ti.com>
Subject: Re: ASoC updates for 3.1
Date: Tue, 4 Oct 2011 15:23:06 +0100 [thread overview]
Message-ID: <20111004142305.GF6934@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <s5hipo4zw12.wl%tiwai@suse.de>
On Tue, Oct 04, 2011 at 04:11:37PM +0200, Takashi Iwai wrote:
> Is a merged branch for 3.2 available so that I can avoid possible
> silly merge mistake?
Yes, I always merge the 3.1 changes up to 3.2 immediately after I commit
them - I was just writing the pull request for that while you sent this
mail.
next prev parent reply other threads:[~2011-10-04 14:23 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-04 13:47 ASoC updates for 3.1 Mark Brown
2011-10-04 14:11 ` Takashi Iwai
2011-10-04 14:23 ` Mark Brown [this message]
2011-10-04 14:38 ` Takashi Iwai
-- strict thread matches above, loose matches on Subject: below --
2011-09-27 12:31 Mark Brown
2011-09-27 12:44 ` Takashi Iwai
2011-09-22 17:17 Mark Brown
2011-09-22 18:02 ` Takashi Iwai
2011-09-26 5:27 ` Scott Jiang
2011-09-26 12:36 ` Mark Brown
2011-09-08 18:22 Mark Brown
2011-08-25 11:07 Mark Brown
2011-08-25 12:08 ` Takashi Iwai
2011-08-21 12:08 Mark Brown
2011-08-21 13:47 ` Takashi Iwai
2011-08-21 16:00 ` Mark Brown
2011-08-21 16:25 ` Takashi Iwai
2011-08-21 16:46 ` Mark Brown
2011-08-12 16:11 Mark Brown
2011-08-12 16:26 ` Takashi Iwai
2011-08-04 4:11 Mark Brown
2011-08-04 14:21 ` Takashi Iwai
2011-07-25 7:05 Mark Brown
2011-07-25 7:42 ` Takashi Iwai
2011-07-18 10:43 Mark Brown
2011-07-18 11:12 ` Takashi Iwai
2011-07-13 23:58 Mark Brown
2011-07-09 9:20 Mark Brown
2011-07-05 6:16 Mark Brown
2011-07-05 6:22 ` Takashi Iwai
2011-06-24 10:36 Mark Brown
2011-06-24 10:59 ` Takashi Iwai
2011-06-10 12:03 Mark Brown
2011-06-10 12:04 ` Mark Brown
2011-06-10 12:23 ` Takashi Iwai
2011-05-30 3:20 Mark Brown
2011-06-02 17:54 ` Takashi Iwai
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=20111004142305.GF6934@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=lrg@ti.com \
--cc=tiwai@suse.de \
/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).