All of lore.kernel.org
 help / color / mirror / Atom feed
From: Liam Girdwood <liam.r.girdwood@linux.intel.com>
To: Jarkko Nikula <jarkko.nikula@linux.intel.com>
Cc: alsa-devel@alsa-project.org, Mark Brown <broonie@kernel.org>
Subject: Re: [PATCH 1/7] ASoC: Intel: Make ADSP memory block allocation more generic
Date: Mon, 27 Oct 2014 10:09:54 +0000	[thread overview]
Message-ID: <1414404594.6917.7.camel@loki> (raw)
In-Reply-To: <5449FF2A.9070200@linux.intel.com>

On Fri, 2014-10-24 at 10:26 +0300, Jarkko Nikula wrote:
> On 10/24/2014 10:22 AM, Jarkko Nikula wrote:
> > Hi Liam
> >
> > On 10/22/2014 02:02 AM, Mark Brown wrote:
> >> On Mon, Oct 20, 2014 at 03:06:46PM +0100, Liam Girdwood wrote:
> >>> Current block allocation is tied to block type and requestor type. 
> >>> Make the
> >>> allocation more generic by removing the struct module parameter and 
> >>> adding
> >>> a generic block allocator structure. Also pass in the list that the 
> >>> blocks
> >>> have to be added too in order to remove dependence on block 
> >>> requestor type.
> >> I'm having trouble apply this - patch 1 manages to apply with some fuzz
> >> but patch 5 is failing.  Probably needs refreshing against Vinod's
> >> recent changes?  I applied everything up to patch 4 (ASoC: Intel: Add
> >> runtime module support).
> >
> > For me sound.git for-next head a929d726a507 don't build anymore. I 
> > have to revert all your four recent patches cd51c82524ff -4. I guess 
> > some patch order or dependency issue since the first patch doesn't 
> > build when applied to topic/intel?
> >
> Ah, nevermind. Mark was dropped these already. I was building at my 
> local copy of for-next branch before patches were dropped.
> 

Yeah, it looks like it was out of sync with Vinod's latest patches so
I'll resend today now that I'm back from holidays.

Liam 

      reply	other threads:[~2014-10-27 10:10 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-20 14:06 [PATCH 1/7] ASoC: Intel: Make ADSP memory block allocation more generic Liam Girdwood
2014-10-20 14:06 ` [PATCH 2/7] ASoC: Intel: update scratch allocator to use generic block allocator Liam Girdwood
2014-10-20 14:06 ` [PATCH 3/7] ASoC: Intel: Add call to calculate offsets internally within the DSP Liam Girdwood
2014-10-20 14:06 ` [PATCH 4/7] ASoC: Intel: Add runtime module support Liam Girdwood
2014-10-20 14:06 ` [PATCH 5/7] ASoC: Intel: Add DMA firmware loading support Liam Girdwood
2014-10-20 14:06 ` [PATCH 6/7] ASoC: Intel: Add runtime module lookup API call Liam Girdwood
2014-10-20 14:06 ` [PATCH 7/7] ASoC: Intel: Provide streams with dynamic module information Liam Girdwood
2014-10-21 23:02 ` [PATCH 1/7] ASoC: Intel: Make ADSP memory block allocation more generic Mark Brown
2014-10-22  9:07   ` Mark Brown
2014-10-24  7:22   ` Jarkko Nikula
2014-10-24  7:26     ` Jarkko Nikula
2014-10-27 10:09       ` Liam Girdwood [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=1414404594.6917.7.camel@loki \
    --to=liam.r.girdwood@linux.intel.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=jarkko.nikula@linux.intel.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.