linux-kernel - Re: [PATCH 1/2] Generic per-device coherent dma allocator

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 for Android: free password hash cracker in your pocket

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

Message-Id: <200807011915.08540.jbarnes@virtuousgeek.org>
Date:	Tue, 1 Jul 2008 19:15:08 -0700
From:	Jesse Barnes <jbarnes@...tuousgeek.org>
To:	Ingo Molnar <mingo@...e.hu>
Cc:	Dmitry Baryshkov <dbaryshkov@...il.com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org, Thomas Gleixner <tglx@...utronix.de>,
	Ingo Molnar <mingo@...hat.com>,
	"H. Peter Anvin" <hpa@...or.com>
Subject: Re: [PATCH 1/2] Generic per-device coherent dma allocator

On Monday, June 30, 2008 3:58 am Ingo Molnar wrote:
> * Dmitry Baryshkov <dbaryshkov@...il.com> wrote:
> > Currently x86_32, sh and cris-v32 provide per-device coherent dma
> > memory allocator. However their implementation is nearly identical.
> > Refactor out common code to be reused by them.
>
> looks good to me in principle.
>
> Andrew, Jesse: i've put this aside into the core/generic-dma-coherent
> git tree which you can check at:
>
>    git://git.kernel.org/pub/scm/linux/kernel/git/tip/linux-2.6-tip.git
> core/generic-dma-coherent
>
> there's some interaction with other x86 bits so i guess it would be best
> to carry this in -tip.
>
> Do the generic bits look good to you? (find the shortlog and diff below)
> It's not yet propagated into linux-next, pending your ack/nak and
> pending some test exposure.

Yeah, looks great to me; if you have dependent changes you can push it; I 
don't think I have anything in my tree that'll cause real trouble.

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/