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] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 28 Jul 2008 19:29:46 -0600
From:	Matthew Wilcox <matthew@....cx>
To:	Jesse Barnes <jbarnes@...tuousgeek.org>
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 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.

-- 
Intel are signing my paycheques ... these opinions are still mine
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours.  We can't possibly take such
a retrograde step."
--
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/