All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Raffaele Recalcati <lamiaposta71@gmail.com>
Cc: davinci-linux-open-source@linux.davincidsp.com,
	Barry Song <21cnbao@gmail.com>,
	Peter Ujfalusi <peter.ujfalusi@nokia.com>,
	alsa-devel@alsa-project.org,
	Eero Nurkkala <ext-eero.nurkkala@nokia.com>,
	Davide Bonfanti <davide.bonfanti@bticino.it>,
	Liam Girdwood <lrg@slimlogic.co.uk>
Subject: Re: [PATCH 1/3] ASoC: soc-core: soc_pcm_ops dynamically allocated
Date: Fri, 16 Jul 2010 16:09:48 +0100	[thread overview]
Message-ID: <20100716150948.GA23183@rakim.wolfsonmicro.main> (raw)
In-Reply-To: <1279291619-5081-2-git-send-email-lamiaposta71@gmail.com>

On Fri, Jul 16, 2010 at 04:46:57PM +0200, Raffaele Recalcati wrote:

>     If soc_pcm_ops is statically allocated, more than one call to soc_new_pcm
>     cause operations overwrite. The problem is overcome usyng dynamic
>     allocation.

As I said previously you're looking for Liam's multi-component work
here rather than this (or at least should be basing your work off his).

  reply	other threads:[~2010-07-16 15:09 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-16 14:46 ASoC DaVinci voicecodec based on copyfromuser Raffaele Recalcati
     [not found] ` <1279291619-5081-1-git-send-email-lamiaposta71-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2010-07-16 14:46   ` [PATCH 1/3] ASoC: soc-core: soc_pcm_ops dynamically allocated Raffaele Recalcati
2010-07-16 15:09     ` Mark Brown [this message]
     [not found]       ` <20100716150948.GA23183-HF5t3jzXg/6ND3a5+9QAFujbO/Zr0HzV@public.gmane.org>
2010-07-16 15:25         ` Raffaele Recalcati
2010-07-16 15:35           ` Mark Brown
2010-07-16 14:46   ` [PATCH 2/3] ASoC: DaVinci: Added support based on copy_from_user instead of DMA Raffaele Recalcati
2010-08-03 15:13     ` Mark Brown
2010-07-16 14:46   ` [PATCH 3/3] ASoC: DaVinci: Voicecodec: Added support based on davinci-pcm-copyfromuser Raffaele Recalcati

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=20100716150948.GA23183@rakim.wolfsonmicro.main \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=21cnbao@gmail.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=davide.bonfanti@bticino.it \
    --cc=davinci-linux-open-source@linux.davincidsp.com \
    --cc=ext-eero.nurkkala@nokia.com \
    --cc=lamiaposta71@gmail.com \
    --cc=lrg@slimlogic.co.uk \
    --cc=peter.ujfalusi@nokia.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.