linux-kernel - Re: [RFC 0/5] tty: move stuff around

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]

Date:	Mon, 30 Aug 2010 00:18:55 +0100
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	Arnd Bergmann <arnd@...db.de>
Cc:	Greg KH <gregkh@...e.de>, linux-kernel@...r.kernel.org
Subject: Re: [RFC 0/5] tty: move stuff around

> Of course, moving stuff around always has the tendency to
> break patches against it, so we might not want to do this after
> all.
> 
> Any other opinions?

Linus actually suggested this should get done in some form a while ago
back when I was tty maintainer but about the same time as I decided not
to be.

>   tty: move tty layer code to drivers/tty

I would be tempted to put the core stuff in /tty as its not drivers

>   tty/vt: move files to drivers/tty/vt/
>   tty/hvc: move files to drivers/tty/hvc
>   tty/hw: move hardware drivers to drivers/tty/hw
>   tty: rearrange Kconfig structure

drivers/serial should also walk into tty I think ?

drivers/pcmcia/serial is a bit trickier but I guess should stay as with
drivers/usb/serial

There are several unbuildable ancient drivers. Perhaps if we are having
the great rename those should simply get deleted first, as there is no
way to test them in their current config ?
--
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/