linux-kernel - Re: [PATCH 0/8] x86 dma_*_coherent rework patchset v2

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:	Thu, 21 Aug 2008 08:07:05 -0700
From:	Jesse Barnes <jbarnes@...tuousgeek.org>
To:	FUJITA Tomonori <fujita.tomonori@....ntt.co.jp>
Cc:	mingo@...e.hu, joerg.roedel@....com, mingo@...hat.com,
	tglx@...utronix.de, hpa@...or.com, linux-kernel@...r.kernel.org,
	iommu@...ts.linux-foundation.org, muli@...ibm.com
Subject: Re: [PATCH 0/8] x86 dma_*_coherent rework patchset v2

On Thursday, August 21, 2008 7:16 am FUJITA Tomonori wrote:
> > > > Jesse, Fujita-san, do these changes look fine to you?
> > >
> > > Yeah, I'll let you push this time. :)
> > >
> > > Signed-off-by:  Jesse Barnes <jbarnes@...tuousgeek.org>
> >
> > with a v2.6.28 ETA, right?
>
> Surely, this patchset should be for 2.6.28.
>
> Can you send this via the x86 tree instead of pci?
>
> - IOMMU code is arch stuff rather than pci.
> - We can avoid a mistake such as the previous one.

Yeah I was thinking 2.6.28 too, via the x86 tree.  The problem last time was 
that I sent it too soon (I misunderstood Ingo when he said it was ready) so 
we broke the build on some non-x86 platforms.  I don't think that'll be an 
issue this time, but we may as well push through x86 anyway; I agree that 
IOMMU is really a platform feature more than a PCI one.

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/