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]
Message-ID: <20080213094403.1d6ebe8c@dhcp-252-066.norway.atmel.com>
Date:	Wed, 13 Feb 2008 09:44:03 +0100
From:	Haavard Skinnemoen <hskinnemoen@...el.com>
To:	"Dan Williams" <dan.j.williams@...el.com>
Cc:	"Olof Johansson" <olof@...om.net>, linux-kernel@...r.kernel.org,
	"Shannon Nelson" <shannon.nelson@...el.com>,
	"David Brownell" <david-b@...bell.net>, kernel@...32linux.org,
	"Francis Moreau" <francis.moro@...il.com>,
	"Paul Mundt" <lethal@...ux-sh.org>,
	"Vladimir A. Barinov" <vbarinov@...mvista.com>,
	"Pierre Ossman" <drzeus-list@...eus.cx>,
	Adrian Bunk <bunk@...sta.de>
Subject: Re: [RFC v3 5/7] dmaengine: Make DMA Engine menu visible for AVR32
 users

On Tue, 12 Feb 2008 15:27:29 -0700
"Dan Williams" <dan.j.williams@...el.com> wrote:

> > > Or just let the subsystem always be available.  
> >
> > It used to be always available, but then it was changed. Assuming there
> > was a reason for this change, I guess we don't want to change it back.
> >  
> 
> Adrian had concerns about users enabling NET_DMA when the hardware
> capability is relatively rare.  So, +1 for HAVE_DMA_DEVICE

Why not introduce a new hidden symbol, e.g. DMA_ENGINE_DRIVER, have all
the drivers select it and let NET_DMA depend on it?

Wait a minute...the Kconfig already does this. What was the problem again?

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ