linux-kernel - Re: [PATCH linux-next] dmaengine: add context parameter fixups

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <1333018785.1820.48.camel@vkoul-udesk3>
Date:	Thu, 29 Mar 2012 16:29:45 +0530
From:	Vinod Koul <vinod.koul@...ux.intel.com>
To:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
Cc:	Takashi Iwai <tiwai@...e.de>, Fabio Estevam <festevam@...il.com>,
	Alexandre Bounine <alexandre.bounine@....com>,
	paul.gortmaker@...driver.com, dan.j.williams@...el.com,
	samuel@...tiz.org, lrg@...com, perex@...ex.cz,
	linux-kernel@...r.kernel.org, linux-next@...r.kernel.org,
	netdev@...r.kernel.org, fabio.estevam@...escale.com,
	alsa-devel@...a-project.org
Subject: Re: [PATCH linux-next] dmaengine: add context parameter fixups

On Wed, 2012-03-28 at 16:51 +0100, Mark Brown wrote:
> On Wed, Mar 28, 2012 at 05:44:22PM +0200, Takashi Iwai wrote:
> > Mark Brown wrote:
> 
> > > 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.
> 
> > How is the situation now?
> 
> > FYI, I'm going to send a pull request to Linus tomorrow or on Friday.
> > If anything needed to be merged in rc1, it must be there in time.
> 
> It's in my tree, I didn't see an enormous rush to get it in TBH.
I should be sending the pull request for slave-dma to Linus this
evening.
Can you please include the fix I did in your tree in your pull request.


-- 
~Vinod

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/