From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: "linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
Eric Millbrandt <emillbrandt@dekaresearch.com>
Subject: Re: [PATCH 0/2 v3] mpc5200 ac97 gpio reset
Date: Tue, 3 Aug 2010 06:52:17 +0100 [thread overview]
Message-ID: <20100803055216.GA25306@rakim.wolfsonmicro.main> (raw)
In-Reply-To: <AANLkTikbHp18uc-idFtEqakoo_0Vdg_rU44xv9uHwkvG@mail.gmail.com>
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. Yeah, probably better to take it via your tree then. I've
> currently got patch 1 in linux-next, but I'll drop it before asking
> benh to pull. Go 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... could you restore the patch to your tree please?
next prev parent reply other threads:[~2010-08-03 5:57 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 [this message]
2010-08-05 12:59 ` Eric Millbrandt
2010-08-06 18:44 ` Grant Likely
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=20100803055216.GA25306@rakim.wolfsonmicro.main \
--to=broonie@opensource.wolfsonmicro.com \
--cc=emillbrandt@dekaresearch.com \
--cc=grant.likely@secretlab.ca \
--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).