linux-kernel - Re: [git pull] PCI code for 2.6.27-rc1

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: <200807281908.51780.jbarnes@virtuousgeek.org>
Date:	Mon, 28 Jul 2008 19:08:51 -0700
From:	Jesse Barnes <jbarnes@...tuousgeek.org>
To:	Matthew Wilcox <matthew@....cx>
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	linux-kernel@...r.kernel.org, linux-pci@...r.kernel.org
Subject: Re: [git pull] PCI code for 2.6.27-rc1

On Monday, July 28, 2008 6:29 pm Matthew Wilcox wrote:
> On Mon, Jul 28, 2008 at 05:50:14PM -0700, Jesse Barnes wrote:
> > Dmitry Baryshkov (7):
> >       generic: per-device coherent dma allocator
> >       x86: use generic per-device dma coherent allocator
> >       Generic dma-coherent: fix DMA_MEMORY_EXCLUSIVE
> >       ARM: support generic per-device coherent dma mem
> >       Sh: use generic per-device coherent dma allocator
> >       Cris: convert to using generic dma-coherent mem allocator
> >       dma-coherent: add documentation to new interfaces
>
> Were these patches posted to linux-pci?  I don't think I ever saw them.

No, but they're not really PCI specific patches.  They did go to lkml several 
times and have been sitting in one of Ingo's test trees for awhile.  There 
are no outstanding complaints that I'm aware of.

Jesse
--
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/