linux-kernel - Re: [PATCH] tty: MAX3100

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.LFD.2.00.0904100808350.4583@localhost.localdomain>
Date:	Fri, 10 Apr 2009 08:21:17 -0700 (PDT)
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Alan Cox <alan@...rguk.ukuu.org.uk>
cc:	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] tty: MAX3100

Btw, Alan, since you're working on those tty drivers, one thing I thought 
I'd ask you is whether you'd be interested in moving the tty drivers to a 
subdirectory of their own.

>From a quick unscientific count, it looks like of the 271 files in 
drivers/char, about 90 are tty/console-related (done by "git grep -l 
'\<tty\>'"), and the rest are pretty random (either literally about random 
hardware or about agp or just odd stuff).

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?

Not a big deal, just wondering.

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