From: Grant Likely <grant.likely@secretlab.ca>
To: Eric Millbrandt <emillbrandt@dekaresearch.com>
Cc: Mark Brown <broonie@opensource.wolfsonmicro.com>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>
Subject: Re: [PATCH 0/2 v3] mpc5200 ac97 gpio reset
Date: Fri, 6 Aug 2010 12:44:59 -0600 [thread overview]
Message-ID: <AANLkTimuW+02aJuK+YcRFTiYdB0=CnLGJs5jfV2=RRfL@mail.gmail.com> (raw)
In-Reply-To: <0A40042D85E7C84DB443060EC44B3FD325420B9123@dekaexchange07.deka.local>
On Thu, Aug 5, 2010 at 6:59 AM, Eric Millbrandt
<emillbrandt@dekaresearch.com> wrote:
>> -----Original Message-----
>> From: linuxppc-dev-bounces+emillbrandt=3Ddekaresearch.com@lists.ozlabs.o=
rg
>> [mailto:linuxppc-dev-
>> bounces+emillbrandt=3Ddekaresearch.com@lists.ozlabs.org] On Behalf Of Ma=
rk
>> Brown
>> Sent: Tuesday, August 03, 2010 01:52
>> To: Grant Likely
>> Cc: linuxppc-dev@lists.ozlabs.org; Eric Millbrandt
>> Subject: Re: [PATCH 0/2 v3] mpc5200 ac97 gpio reset
>>
>> On Sat, Jul 31, 2010 at 10:42:15PM -0600, Grant Likely wrote:
>> > On Sun, Jun 27, 2010 at 4:01 PM, Mark Brown
>>
>> > > I'm a little concerned with a collision with multi codec here. It'd
>> > > be handy if you could keep it separate in case it needs merging
>> > > into both trees (or we could merge via ASoC only).
>>
>> > Hmmm. =A0Yeah, probably better to take it via your tree then. =A0I've
>> > currently got patch 1 in linux-next, but I'll drop it before asking
>> > benh to pull. =A0Go ahead and add my acked-by.
>>
>> Looks like multi-component is slightly too late for .36 and I don't have
>> the original patch any more since it looked like you were going to be
>> carrying it... =A0could you restore the patch to your tree please?
>
> <ping> Grant, are you going to pick up this series for .36?
Yes, working on it... :-)
g.
prev parent reply other threads:[~2010-08-06 18:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-15 16:05 [PATCH 0/2 v3] mpc5200 ac97 gpio reset Eric Millbrandt
2010-06-15 16:05 ` [PATCH 1/2 v3] powerpc/5200: add mpc5200_psc_ac97_gpio_reset Eric Millbrandt
2010-06-15 16:05 ` [PATCH 2/2 v4] sound/soc: mpc5200_psc_ac97: Use gpio pins for cold reset Eric Millbrandt
2010-06-15 21:53 ` [PATCH 1/2 v4] powerpc/5200: add mpc5200_psc_ac97_gpio_reset Eric Millbrandt
2010-06-22 23:00 ` [PATCH 0/2 v3] mpc5200 ac97 gpio reset Mark Brown
2010-06-25 23:04 ` Grant Likely
2010-06-27 22:01 ` Mark Brown
2010-08-01 4:42 ` Grant Likely
2010-08-03 5:52 ` Mark Brown
2010-08-05 12:59 ` Eric Millbrandt
2010-08-06 18:44 ` Grant Likely [this message]
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='AANLkTimuW+02aJuK+YcRFTiYdB0=CnLGJs5jfV2=RRfL@mail.gmail.com' \
--to=grant.likely@secretlab.ca \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=emillbrandt@dekaresearch.com \
--cc=linuxppc-dev@lists.ozlabs.org \
/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).