From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Nicolas Pitre <nico@fluxnic.net>
Cc: Dmitry Safonov <dima@arista.com>, Jiri Slaby <jslaby@suse.cz>,
Mark Rutland <mark.rutland@arm.com>,
Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>,
Tycho Andersen <tycho@tycho.ws>, Dave Mielke <dave@mielke.cc>,
linux-kernel@vger.kernel.org
Subject: Re: commit 83d817f410 broke my ability to use Linux with a braille display
Date: Sat, 12 Jan 2019 09:08:25 +0100 [thread overview]
Message-ID: <20190112080825.GA530@kroah.com> (raw)
In-Reply-To: <nycvar.YSQ.7.76.1901111503390.2566@knanqh.ubzr>
On Fri, Jan 11, 2019 at 03:10:04PM -0500, Nicolas Pitre wrote:
> On Fri, 11 Jan 2019, Greg Kroah-Hartman wrote:
>
> > On Fri, Jan 11, 2019 at 01:33:09PM -0500, Nicolas Pitre wrote:
> > > I use Linux with the help of a braille display and the brltty daemon. It
> > > turns out that the latest mainline kernel I can work with comes from
> > > commit 231f8fd0cc. Anything past that and I lose the ability to read the
> > > console barely a few seconds after the system has booted as brltty is
> > > thrown a wrench and the braille display becomes completely inoperable.
> >
> > Please try the patch below, it was just queued up to my tree and should
> > resolve the issue. If not, please let us know.
>
> Yes, it works. Thanks.
>
> I also re-validated all the vt/vcs patches I sent you this week for
> which I started entertaining some doubts about their stability. But they
> all work fine again with the tty fix applied.
Great, thanks for testing, I will get this patch to Linus soon.
greg k-h
prev parent reply other threads:[~2019-01-12 8:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-11 18:33 commit 83d817f410 broke my ability to use Linux with a braille display Nicolas Pitre
2019-01-11 19:11 ` Vito Caputo
2019-01-11 19:32 ` Nicolas Pitre
2019-01-11 19:32 ` Greg Kroah-Hartman
2019-01-11 20:10 ` Nicolas Pitre
2019-01-12 8:08 ` Greg Kroah-Hartman [this message]
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=20190112080825.GA530@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=dave@mielke.cc \
--cc=dima@arista.com \
--cc=jslaby@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=nico@fluxnic.net \
--cc=penguin-kernel@i-love.sakura.ne.jp \
--cc=tycho@tycho.ws \
/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).