linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Laxman Dewangan <ldewangan@nvidia.com>
Cc: "perex@perex.cz" <perex@perex.cz>,
	"tiwai@suse.de" <tiwai@suse.de>, "lrg@ti.com" <lrg@ti.com>,
	"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Stephen Warren <swarren@nvidia.com>
Subject: Re: [PATCH] ASoC: snd_dmaengine: add common api for pcm_mmap
Date: Thu, 28 Jun 2012 13:02:45 +0100	[thread overview]
Message-ID: <20120628120245.GF28922@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <4FEC468A.3080607@nvidia.com>

[-- Attachment #1: Type: text/plain, Size: 571 bytes --]

On Thu, Jun 28, 2012 at 05:26:58PM +0530, Laxman Dewangan wrote:

> Other driver which can use this API are davinci, OMAP, samsung but
> because they are not using the snd_dmaengine_pcm driver's api as of
> now so not be very much useful for them.

There's no reason why we can't factor out more common code - this is
essentially what Lars-Peter was saying.

> Should I send one patch per driver change or squash all 4 file
> changes in one patch? Whatever will be easy or recommended?

It doesn't really matter that much, but please take on board
Lars-Peter's comments.

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

  reply	other threads:[~2012-06-28 12:02 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-28  7:01 [PATCH] ASoC: snd_dmaengine: add common api for pcm_mmap Laxman Dewangan
2012-06-28 10:51 ` Mark Brown
2012-06-28 11:56   ` Laxman Dewangan
2012-06-28 12:02     ` Mark Brown [this message]
2012-06-28 12:07       ` Laxman Dewangan
2012-06-28 12:44     ` Lars-Peter Clausen
2012-06-28 14:03       ` [alsa-devel] " Takashi Iwai
2012-06-28 11:09 ` Lars-Peter Clausen
2012-06-28 12:15   ` Takashi Iwai
2012-06-28 12:18     ` [alsa-devel] " Mark Brown
2012-06-28 12:30       ` Lars-Peter Clausen
2012-06-28 12:28         ` Mark Brown
2012-06-28 12:35           ` Laxman Dewangan
2012-06-28 12:57             ` Takashi Iwai
2012-06-28 13:04               ` Laxman Dewangan
2012-06-28 13:28                 ` Takashi Iwai
2012-06-28 13:36                   ` Laxman Dewangan
2012-06-28 13:51                     ` Takashi Iwai
2012-06-28 14:00                       ` Laxman Dewangan
2012-06-28 14:10                         ` Takashi Iwai
2012-06-29 16:42                       ` Lars-Peter Clausen
2012-07-02 12:50         ` Marek Szyprowski
2012-06-28 12:32       ` Clemens Ladisch

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=20120628120245.GF28922@opensource.wolfsonmicro.com \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=ldewangan@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lrg@ti.com \
    --cc=perex@perex.cz \
    --cc=swarren@nvidia.com \
    --cc=tiwai@suse.de \
    /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).