From: Kevin Hilman <khilman@deeprootsystems.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: alsa-devel@alsa-project.org,
Sudhakar Rajashekhara <sudhakar.raj@ti.com>,
davinci-linux-open-source@linux.davincidsp.com
Subject: Re: [PATCH 1/2] ASoC: davinci: update after EDMA interface changes
Date: Mon, 06 Jul 2009 15:35:59 -0700 [thread overview]
Message-ID: <87zlbhjv74.fsf@deeprootsystems.com> (raw)
In-Reply-To: <20090706222512.GH25548@sirena.org.uk> (Mark Brown's message of "Mon\, 6 Jul 2009 23\:25\:12 +0100")
Mark Brown <broonie@opensource.wolfsonmicro.com> writes:
> On Mon, Jul 06, 2009 at 03:19:01PM -0700, Kevin Hilman wrote:
>
>> So should I queue this up along with my changes, or do you want to
>> merge this into asoc?
>
> It needs to go along with your changes at least to preserve bisect (it
> should really be in the same commit that changes the API from that point
> of view).
OK, it was originally part of the same patch, but I separated it out
thinking that the sound/* part would go upstream separately.
I'll merge it back into the original commit and update davinci-next.
> But see my reply to Troy's post - he's got some further ASoC
> changes which depend on the new API and complicate matters a little.
OK, will reply there.
Kevin
prev parent reply other threads:[~2009-07-06 22:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-06 22:02 [PATCH 0/2] davinci ASoC interface changes Kevin Hilman
2009-07-06 22:02 ` [PATCH 1/2] ASoC: davinci: update after EDMA " Kevin Hilman
2009-07-06 22:02 ` [PATCH 2/2] ASoC: DaVinci: Change default output volume Kevin Hilman
2009-07-06 22:07 ` Mark Brown
2009-07-06 22:08 ` [PATCH 1/2] ASoC: davinci: update after EDMA interface changes Mark Brown
2009-07-06 22:19 ` Kevin Hilman
2009-07-06 22:25 ` Mark Brown
2009-07-06 22:35 ` Kevin Hilman [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=87zlbhjv74.fsf@deeprootsystems.com \
--to=khilman@deeprootsystems.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=davinci-linux-open-source@linux.davincidsp.com \
--cc=sudhakar.raj@ti.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.