linux-kernel - Re: [PATCH 1/3] dma: add dma_flags_set/get

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: <20071017131054.d3d88c62.akpm@linux-foundation.org>
Date:	Wed, 17 Oct 2007 13:10:54 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	akepner@....com
Cc:	tony.luck@...el.com, grundler@...isc-linux.org,
	jbarnes@...tuousgeek.org, jes@....com, randy.dunlap@...cle.com,
	rdreier@...co.com, James.Bottomley@...eleye.com,
	davem@...emloft.net, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/3] dma: add dma_flags_set/get_*() interfaces

On Wed, 17 Oct 2007 09:03:27 -0700
akepner@....com wrote:

> > 
> > What would be the cost of doing this cleanly and either redefining
> > dma_data_direction to be a field-of-bits or just leave dma_data_direction
> > alone (it is quite unrelated to this work, isn't it?) and adding new
> > fields/arguments to manage this new functionality?
> 
> It'd be significantly more work to do change or add arguments 
> to the dma_map_* functions. But if that's what I need to do to 
> get this accepted, I'll back up and have another go at it.

I don't have any particularly strong opinions on which would be the best
way to clean this up.  Hopefully someone who is more involved with the DMA
mapping interfaces can help out.

It wouldn't be efficient for you to implement something new, only to have
it criticized again.  I'd suggest that you come up with a concrete
design, describe to us what you propose to do and let's take it from there.

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