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: <201008302333.22447.arnd@arndb.de>
Date:	Mon, 30 Aug 2010 23:33:22 +0200
From:	Arnd Bergmann <arnd@...db.de>
To:	Greg KH <gregkh@...e.de>, Jiri Slaby <jslaby@...e.cz>,
	Alan Cox <alan@...rguk.ukuu.org.uk>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: [RFC 0/5] tty: move stuff around

On Monday 30 August 2010 20:47:37 Greg KH wrote:
> On Sun, Aug 29, 2010 at 11:06:30PM +0200, Arnd Bergmann wrote:
> > Hi Greg,
> > 
> > After fighting with the BKL removal in tty, I realized that the
> > files in drivers/char could use a reorganization to split the
> > tty files from those drivers that have nothing to do with ttys.
> 
> <snip>
> 
> I like the idea, and after you've worked out with Alan which ones should
> be "deleted" and others moved around, I'll be glad to apply these types
> of patches.
> 
> Oh, we shouldn't just delete the drivers, we can move them to
> drivers/staging/ where they will then be removed after 2 kernel releases
> if no one steps up to fix/maintain them.  That's the "proper" way to
> depreciate a driver.

Ok, I was already wondering if this would be the right way.


With the feedback I have so far, I think we have

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

cyclades,moxa,mxser     -> drivers/tty/hw/

stallion,istallion,
epca,specialix,ip2,
riscom,isicom           -> drivers/staging/tty/*

generic_serial,vme_scc,
ser_a2232,sx,rio        -> drivers/staging/generic_serial/*

amiserial,nozomi,
serial167,synclink      -> drivers/tty/hw (?)

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

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

I'll wait a few days for other suggestions and then prepare
a new patch series.

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