From: Liam Girdwood <lrg@slimlogic.co.uk>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: Takashi Iwai <tiwai@suse.de>, alsa-devel <alsa-devel@alsa-project.org>
Subject: Re: [GIT PULL] ASoC updates for 2.6.36
Date: Mon, 02 Aug 2010 11:45:49 +0100 [thread overview]
Message-ID: <1280745949.3095.47.camel@odin> (raw)
In-Reply-To: <24C97B09-0B9B-4115-82DF-0528B6B55EE6@opensource.wolfsonmicro.com>
On Mon, 2010-08-02 at 11:33 +0100, Mark Brown wrote:
> On 2 Aug 2010, at 11:30, Liam Girdwood wrote:
>
> > Ok, the multi-component branch does touch arch quite a bit as we are
> > adding platform devices for all our components. So it's probably safer
> > for merging (after your pull request) in the for 2.6.37 period to reduce
> > any merge conflict with arch.
>
> > Fwiw, the release yesterday did take me a little by surprise as I was at
> > least expecting an rc7 and a little extra time for multi-comp ;)
>
> In that case I guess I'll send a pull request with WM8741 tomorrow and
> send you the multi-component updates for it separately if that's OK
> with you (I'm about to crash, just got in from 16 hours of flying)?
Yep, that's cool.
Thanks
Liam
--
Freelance Developer, SlimLogic Ltd
ASoC and Voltage Regulator Maintainer.
http://www.slimlogic.co.uk
next prev parent reply other threads:[~2010-08-02 10:45 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-02 9:53 [GIT PULL] ASoC updates for 2.6.36 Liam Girdwood
2010-08-02 10:13 ` Takashi Iwai
2010-08-02 10:30 ` Liam Girdwood
2010-08-02 10:33 ` Mark Brown
2010-08-02 10:45 ` Liam Girdwood [this message]
2010-08-02 16:24 ` Timur Tabi
2010-08-02 17:39 ` Timur Tabi
-- strict thread matches above, loose matches on Subject: below --
2010-07-21 12:38 Liam Girdwood
2010-07-21 13:02 ` Takashi Iwai
2010-06-24 9:09 Liam Girdwood
2010-06-24 10:50 ` Takashi Iwai
2010-06-07 10:14 Liam Girdwood
2010-06-07 16:41 ` Takashi Iwai
2010-05-31 10:29 Liam Girdwood
2010-05-31 16:14 ` 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=1280745949.3095.47.camel@odin \
--to=lrg@slimlogic.co.uk \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.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