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
| ||
|
Date: Sat, 11 Apr 2009 01:00:39 +0100 From: Alan Cox <alan@...rguk.ukuu.org.uk> To: Linus Torvalds <torvalds@...ux-foundation.org> Cc: linux-kernel@...r.kernel.org Subject: Re: [PATCH] tty: MAX3100 > So I'm wondering if it would make sense to do a drivers/tty for the core > tty (ldisc, tty_io etc) stuff, and perhaps move some of the non-core > (serial) drivers into drivers/serial. > > I don't know, for example, why drivers/char/stallion.c is not in > drivers/serial. Just historical reasons, or an actual reason? drivers/serial is the stuff using the uart layer drivers/usb/serial is the stuff using the USB serial layer drivers/char is the stuff using neither (plus exceptions and bits hiding in arch and stuff) It probably will make sense as everything is slowly getting dragged kicking and screaming to the point where all of these are a struct tty_port with other stuff attached but for the moment its actually sort of convenient to keep them apart. Alan -- 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