From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] tty: the briq panel isn't a tty, make it use its own locking
Date: Fri, 24 Feb 2012 12:37:17 +1100 [thread overview]
Message-ID: <1330047437.20389.40.camel@pasglop> (raw)
In-Reply-To: <20120223225602.747c31df@pyramind.ukuu.org.uk>
On Thu, 2012-02-23 at 22:56 +0000, Alan Cox wrote:
> > 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
Just remove the driver, I don't think anybody cares.
Cheers,
Ben.
next prev parent reply other threads:[~2012-02-24 1:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-23 13:39 [PATCH] tty: the briq panel isn't a tty, make it use its own locking Alan Cox
2012-02-23 20:42 ` Benjamin Herrenschmidt
2012-02-23 22:56 ` Alan Cox
2012-02-24 1:08 ` Josh Boyer
2012-02-24 1:37 ` Benjamin Herrenschmidt [this message]
2012-02-29 20:21 ` Greg KH
-- strict thread matches above, loose matches on Subject: below --
2012-02-23 12:34 Alan Cox
2012-02-23 12:37 ` Jiri Slaby
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1330047437.20389.40.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).