From: Vinod Koul <vinod.koul@linux.intel.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.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 15:24:30 +0530 [thread overview]
Message-ID: <1332755670.19804.91.camel@vkoul-udesk3> (raw)
In-Reply-To: <20120326094200.GA3098@opensource.wolfsonmicro.com>
On Mon, 2012-03-26 at 10:42 +0100, Mark Brown wrote:
> 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.
I should have noticed that sound needs update as well :(
Now either I drop these from 3.4 or merge Linus's tree and apply
Alexandre's fix (as that is the right fix rather than one in asoc tree)
And since this was required for RIO patches which are still WIP, I think
I am leaning towards former.
--
~Vinod
next prev parent reply other threads:[~2012-03-26 9:54 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
2012-03-26 9:54 ` Vinod Koul [this message]
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=1332755670.19804.91.camel@vkoul-udesk3 \
--to=vinod.koul@linux.intel.com \
--cc=alexandre.bounine@idt.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--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 \
/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