alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Liam Girdwood <lrg@ti.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: [PATCH] ASoC: dapm: Add API call to query valid DAPM paths.
Date: Thu, 8 Mar 2012 12:05:54 +0000	[thread overview]
Message-ID: <20120308120554.GL3638@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1331206950.3782.5.camel@odin>


[-- Attachment #1.1: Type: text/plain, Size: 938 bytes --]

On Thu, Mar 08, 2012 at 11:42:30AM +0000, Liam Girdwood wrote:
> On Wed, 2012-03-07 at 19:15 +0000, Mark Brown wrote:

> > I might be blind but I think the hunk that actually declares the widget
> > list got dropped from the header...  probably in some other part of the
> > series you haven't pushed out yet?

> I had to double check myself to be sure and Stephen added it a while
> back :-

> fafd2176f72148e83c64a1f818ff33fceed83d08

Oh, sorry about that - I didn't check the actual code for that one as I
saw you adding the forward declaration and normally we're fairly good
about always adding those so I figured it was a missing diff hunk.

> > > +	dapm_reset(card);

> > This function isn't in mainline, another patch series reordering thing I
> > expect.  

> It's in 6c120e19fa587710d80757a6e364961a017fb6c3

This one I definitely did check, must've been on a separate branch and
didn't notice properly.

[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]



      reply	other threads:[~2012-03-08 12:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-07 17:55 [PATCH] ASoC: dapm: Add API call to query valid DAPM paths Liam Girdwood
2012-03-07 19:15 ` Mark Brown
2012-03-08 11:42   ` Liam Girdwood
2012-03-08 12:05     ` Mark Brown [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=20120308120554.GL3638@opensource.wolfsonmicro.com \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=lrg@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 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).