From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Vinod Koul <vinod.koul@linux.intel.com>
Cc: Fabio Estevam <festevam@gmail.com>,
Alexandre Bounine <alexandre.bounine@idt.com>,
paul.gortmaker@windriver.com, dan.j.williams@intel.com,
samuel@sortiz.org, lrg@ti.com, perex@perex.cz, tiwai@suse.de,
linux-kernel@vger.kernel.org, linux-next@vger.kernel.org,
netdev@vger.kernel.org, fabio.estevam@freescale.com,
alsa-devel@alsa-project.org
Subject: Re: [PATCH linux-next] dmaengine: add context parameter fixups
Date: Mon, 26 Mar 2012 10:42:01 +0100 [thread overview]
Message-ID: <20120326094200.GA3098@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1332740082.19804.15.camel@vkoul-udesk3>
[-- Attachment #1: Type: text/plain, Size: 488 bytes --]
On Mon, Mar 26, 2012 at 11:04:42AM +0530, Vinod Koul wrote:
> On Sat, 2012-03-24 at 12:23 -0300, Fabio Estevam wrote:
> > http://permalink.gmane.org/gmane.linux.alsa.devel/96215
> And this seems to be linux-next.
> Mark, Is this part of the sound updates that went to Linus?
No, not yet - it was only sent after the merge window. Quite why nobody
managed to notice it before then I don't know. It'll go to him soon, or
at least to Takashi, but don't know if it'll make -rc1 or not.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-03-26 9:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-23 14:00 [PATCH linux-next] dmaengine: add context parameter fixups Alexandre Bounine
2012-03-24 0:53 ` Mark Brown
2012-03-24 15:23 ` Fabio Estevam
2012-03-26 5:34 ` Vinod Koul
2012-03-26 9:42 ` Mark Brown [this message]
2012-03-26 9:54 ` Vinod Koul
2012-03-26 10:33 ` Mark Brown
2012-03-26 10:48 ` Vinod Koul
2012-03-26 11:01 ` Mark Brown
2012-03-26 11:07 ` Vinod Koul
2012-03-26 13:14 ` Bounine, Alexandre
2012-03-28 15:44 ` Takashi Iwai
2012-03-28 15:51 ` Mark Brown
2012-03-29 10:59 ` Vinod Koul
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=20120326094200.GA3098@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alexandre.bounine@idt.com \
--cc=alsa-devel@alsa-project.org \
--cc=dan.j.williams@intel.com \
--cc=fabio.estevam@freescale.com \
--cc=festevam@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=lrg@ti.com \
--cc=netdev@vger.kernel.org \
--cc=paul.gortmaker@windriver.com \
--cc=perex@perex.cz \
--cc=samuel@sortiz.org \
--cc=tiwai@suse.de \
--cc=vinod.koul@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 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).