| 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
| ||
|
Message-ID: <s5hzlqjz74d.wl%tiwai@suse.de> Date: Wed, 21 May 2008 23:20:50 +0200 From: Takashi Iwai <tiwai@...e.de> To: linux-kernel@...r.kernel.org Cc: Linus Torvalds <torvalds@...ux-foundation.org>, alsa-devel@...a-project.org, perex@...ex.cz Subject: Moving sound/* to drivers/ ? While we are at the issue ALSA HG <-> GIT transition... One thing that annoys me sometimes is that the sound driver codes are on a different subdirectory than other normal drivers, namely under /sound. I don't remember exactly why it came there, but this often makes people forget to change the necessary code for the sound subsystem, or slip from the statistics (I'm not sure whether Linus counted sound/* with recent his posts). If I understand correctly, with git, we can move the files in relatively little costs. So, what about moving sound/* back to drivers/sound/* or drivers/media/sound/*? Of course, the primary question is whether it's really worth. The obvious drawback is that patches won't be applicable after the move. So, if we do it, doing at the last seems practical. But, this can be a bit problem with keeping such a change on linux-next until the next merge... And, another question is to where. drivers/sound or drivers/media/sound, or whatever. Any comments appreciated. thanks, Takashi -- 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