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]

Message-ID: <20100830232800.3cb768fc@lxorguk.ukuu.org.uk>
Date:	Mon, 30 Aug 2010 23:28:00 +0100
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	Arnd Bergmann <arnd@...db.de>
Cc:	Greg KH <gregkh@...e.de>, Jiri Slaby <jslaby@...e.cz>,
	linux-kernel@...r.kernel.org
Subject: Re: [RFC 0/5] tty: move stuff around

> drivers/char/tty_*      -> tty/*
> drivers/char/{vt stuff} -> tty/vt/
> drivers/char/hvc_*      -> drivers/tty/hvc/hvc_*
> drivers/serial/*        -> drivers/tty/serial/*

There are dead bits in there too we should prune 68xxx stuff mostly

> drivers/usb/serial      -> drivers/usb/serial
> 
> cyclades,moxa,mxser     -> drivers/tty/hw/
> 
> stallion,istallion,
> epca,specialix,ip2,
> riscom,isicom           -> drivers/staging/tty/*

isicom has users and gets tested a bit, not sure about ip2/specialix.

> generic_serial,vme_scc,
> ser_a2232,sx,rio        -> drivers/staging/generic_serial/*
> 
> amiserial,nozomi,
> serial167,synclink      -> drivers/tty/hw (?)

Why /hw - its a tty driver so drivers/tty - the non hw stuff is now in
tty/

serial167 is dead/staging stuff, synclink* are used

> bfin_jtag_comm          -> drivers/tty/hvc/hvc_bfin_jtag (?)

Nothing to do with hvc

> rocket,ipwireless       -> drivers/staging/tty/* (?)

Rocket is used, ipwireless I think is also used

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/