From: Steven Rostedt <rostedt@goodmis.org>
To: Samuel Thibault <samuel.thibault@ens-lyon.org>
Cc: Petr Mladek <pmladek@suse.com>,
Aleksey Makarov <aleksey.makarov@linaro.org>,
linux-serial@vger.kernel.org, Joe Perches <joe@perches.com>,
linux-kernel@vger.kernel.org
Subject: Re: Does braille console work?
Date: Fri, 17 Mar 2017 09:02:08 -0400 [thread overview]
Message-ID: <20170317090208.437d4e10@gandalf.local.home> (raw)
In-Reply-To: <20170317094051.lpdu4pjloboaikgr@var.youpi.perso.aquilenet.fr>
On Fri, 17 Mar 2017 10:40:51 +0100
Samuel Thibault <samuel.thibault@ens-lyon.org> wrote:
> Petr Mladek, on ven. 17 mars 2017 10:35:44 +0100, wrote:
> > Anyway, the feature is not usable at the moment. Samuel, would
> > you be able to fix and test it, please?
>
> Sure, it's already on my TODO list, I will do when I get the time.
>
Yes please. There's no reason to keep that code if it's been broken for
3 years and nobody noticed. In fact, keeping it may actually make it
more difficult to add accessibility in the future. Methodologies may
change and the old broken code (that we've been complicating all other
code with), may actually become a hindrance to a new methodology.
Either keep it updated, or get rid of it. Getting rid of the
complications it adds to the core code, and let the core code become
more simplified may actually end up being easier to add accessibility
in the future, than keeping the old cruft around.
-- Steve
next prev parent reply other threads:[~2017-03-17 13:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-16 14:02 Does braille console work? Aleksey Makarov
2017-03-17 0:53 ` Samuel Thibault
2017-03-17 9:00 ` Aleksey Makarov
2017-03-17 9:16 ` Samuel Thibault
2017-03-17 9:35 ` Petr Mladek
2017-03-17 9:40 ` Samuel Thibault
2017-03-17 13:02 ` Steven Rostedt [this message]
2017-03-19 14:41 ` Samuel Thibault
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=20170317090208.437d4e10@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=aleksey.makarov@linaro.org \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=pmladek@suse.com \
--cc=samuel.thibault@ens-lyon.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