linux-kernel - Re: Moving sound/* to drivers/ ?

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: <alpine.LNX.1.10.0805221735570.9332@fbirervta.pbzchgretzou.qr>
Date:	Thu, 22 May 2008 17:50:29 +0200 (CEST)
From:	Jan Engelhardt <jengelh@...ozas.de>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
cc:	Takashi Iwai <tiwai@...e.de>,
	Rene Herman <rene.herman@...access.nl>,
	Jeff Garzik <jeff@...zik.org>, linux-kernel@...r.kernel.org,
	alsa-devel@...a-project.org, perex@...ex.cz
Subject: Re: Moving sound/* to drivers/ ?


On Thursday 2008-05-22 17:04, Linus Torvalds wrote:
>On Thu, 22 May 2008, Jan Engelhardt wrote:
>> 
>> I am in favor of keeping /sound around with the
>> non-hardware-dependent code, much like /block does with regard to
>> /drivers/block.
>
>I'd personally *much* rather have just one subdirectory.
>[...] BUT:
> - perhaps more importantly, it's totally different from 'sound' in that 
>   the block/ and drivers/block/ maintainership is actually *separate*.
>[...]
>So I'd personally much rather see just one drivers/sound/ than have this 
>split up.

Surveille et rapport.

I took a look at how FreeBSD does this, just for comparison.
They have a single ${src}/dev/sound, but also no split "net" otoh
afaics. As always, if you think Linux should have a drivers/sound/,
just direct your lieutenants to do so.
--
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/