alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	alsa-devel@alsa-project.org, Kukjin Kim <kgene.kim@samsung.com>,
	Vinod Koul <vinod.koul@intel.com>,
	linux-kernel@vger.kernel.org,
	Peter Ujfalusi <peter.ujfalusi@ti.com>,
	linux-next@vger.kernel.org, Liam Girdwood <lrg@ti.com>
Subject: Re: [PATCH 0/2] dmaengine: Fix compillation issues in device_prep_dma_cyclic()
Date: Tue, 25 Sep 2012 12:19:37 +0100	[thread overview]
Message-ID: <20120925111937.GA32685@sirena.org.uk> (raw)
In-Reply-To: <s5h8vbz8fa7.wl%tiwai@suse.de>

On Mon, Sep 24, 2012 at 08:08:32PM +0200, Takashi Iwai wrote:
> At Mon, 24 Sep 2012 10:17:15 +0200,

> > Mark, could you tell me when it's ready?  Since I'll be off from
> > tomorrow, I'd like to resolve sooner.

> My time is up, so I merged Peter's two patches on the top of for-next
> branch of sound git tree now.  Mark, please pull them to your tree if
> needed.

Oh, well.  I was travelling for the entire time between Peter posting
the patches and you applying them :/

  reply	other threads:[~2012-09-25 11:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20120924133923.130c4db72aa8105cb5647d7a@canb.auug.org.au>
2012-09-24  7:58 ` [PATCH 0/2] dmaengine: Fix compillation issues in device_prep_dma_cyclic() Peter Ujfalusi
2012-09-24  7:58   ` [PATCH 1/2] dmaengine: Add flags parameter to dmaengine_prep_dma_cyclic() Peter Ujfalusi
2012-09-24  7:58   ` [PATCH 2/2] ARM: SAMSUNG: dma-ops: Fix dmaengine_prep_dma_cyclic() parameter list Peter Ujfalusi
2012-09-24  8:17   ` [PATCH 0/2] dmaengine: Fix compillation issues in device_prep_dma_cyclic() Takashi Iwai
2012-09-24 18:08     ` Takashi Iwai
2012-09-25 11:19       ` Mark Brown [this message]
2012-09-24  8:40   ` Vinod Koul
2012-10-12 16:44   ` [alsa-devel] " Tabi Timur-B04825

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=20120925111937.GA32685@sirena.org.uk \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=kgene.kim@samsung.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=lrg@ti.com \
    --cc=peter.ujfalusi@ti.com \
    --cc=sfr@canb.auug.org.au \
    --cc=tiwai@suse.de \
    --cc=vinod.koul@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 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).