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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 23 Feb 2012 20:08:14 -0500
From:	Josh Boyer <jwboyer@...il.com>
To:	Alan Cox <alan@...rguk.ukuu.org.uk>
Cc:	Benjamin Herrenschmidt <benh@...nel.crashing.org>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] tty: the briq panel isn't a tty, make it use its own locking

On Thu, Feb 23, 2012 at 5:56 PM, Alan Cox <alan@...rguk.ukuu.org.uk> wrote:
> 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

I'd vote for out to staging.  Don't rely on BenH to make sane decisions when
it comes to deprecating stuff nobody uses anymore.  I mean... he's only just
now dropping iSeries support.

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