linux-kernel - Re: [PATCH] tty: the briq panel isn't a tty, make it use its own locking

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: <20120223225602.747c31df@pyramind.ukuu.org.uk>
Date:	Thu, 23 Feb 2012 22:56:02 +0000
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	Benjamin Herrenschmidt <benh@...nel.crashing.org>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] tty: the briq panel isn't a tty, make it use its own
 locking

On Fri, 24 Feb 2012 07:42:27 +1100
Benjamin Herrenschmidt <benh@...nel.crashing.org> wrote:

> On Thu, 2012-02-23 at 13:39 +0000, Alan Cox wrote:
> > From: Alan Cox <alan@...ux.intel.com>
> > 
> > The driver appears to be terminall broken, if nobody is maintaining it then
> > perhaps it should go into staging and the out-tray.
> 
> Hrm, I don't think anybody maintains it but I do have a BriQ somewhere
> in storage, so I suppose I could pick it up, not that I need another
> crap driver to deal with right now though...

In which case can we just stuff it into the tree, or take the briq driver
out into staging as this is the last blocker on tackling the tty_lock
entirely in the tty layer

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/