| 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
| ||
|
Message-ID: <4FFD5202.9080206@nvidia.com> Date: Wed, 11 Jul 2012 15:44:26 +0530 From: Laxman Dewangan <ldewangan@...dia.com> To: Mark Brown <broonie@...nsource.wolfsonmicro.com> CC: "grant.likely@...retlab.ca" <grant.likely@...retlab.ca>, "spi-devel-general@...ts.sourceforge.net" <spi-devel-general@...ts.sourceforge.net>, "swarren@...dotorg.org" <swarren@...dotorg.org>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, "linux-tegra@...r.kernel.org" <linux-tegra@...r.kernel.org> Subject: Re: [PATCH RESEND] spi: tegra: use dmaengine based dma driver On Wednesday 11 July 2012 03:45 PM, Mark Brown wrote: > * PGP Signed by an unknown key > > On Wed, Jul 11, 2012 at 03:30:42PM +0530, Laxman Dewangan wrote: >> On Wednesday 11 July 2012 03:25 PM, Mark Brown wrote: > >> I believe you have applied for the ASoC one. This is for spi one. > No, there's a dmaengine patch in my SPI branch too which I applied > yesterday. > > git://git.kernel.org/pub/scm/linux/kernel/git/broonie/misc.git spi-next > Looked at your misc/spi-next and you have already applied. This was just resend. Thanks for taking care. > > I'm sorry, I can't parse this sentance at all. > Just wanted to know that spi changes will be in regulator/for-next or some other tree. It is in misc/spi-next. -- 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/
Powered by blists - more mailing lists