From: Okash Khawaja <okash.khawaja@gmail.com>
To: Samuel Thibault <samuel.thibault@ens-lyon.org>
Cc: speakup@linux-speakup.org, William Hubbs <w.d.hubbs@gmail.com>
Subject: Re: TODO file
Date: Fri, 15 Mar 2019 10:57:35 +0000 [thread overview]
Message-ID: <20190315105735.41e84bfe@narunkot> (raw)
In-Reply-To: <20190314154419.6oysgov7yfichxrx@function>
On Thu, 14 Mar 2019 16:44:19 +0100
Samuel Thibault <samuel.thibault@ens-lyon.org> wrote:
> Okash Khawaja, le jeu. 14 mars 2019 15:43:03 +0000, a ecrit:
> > That sounds good. I'll start a thread with Greg and see where we
> > go.
>
> Remember to keep in Cc the speakup, the staging, and the linux-kernel
> mailing lists.
>
Thanks for the heads up. Will do that.
I am putting together the email with status for each item in TODO file.
I just have two more queries.
1. What are our options for internal synths which still use direct
communication with hardware: acntpc, decpc, dtlk and keypc?
2. What is status of output buffer getting garbled in SMP systems?
Here's the text from TODO file:
"Another issue seems to only happen on SMP systems. It seems
that text in the output buffer gets garbled because a lock is not set.
This bug happens regularly, but no one has been able to find a situation
which produces it consistently."
Thanks,
Okash
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
Okash Khawaja
` Samuel Thibault
` Okash Khawaja
` Samuel Thibault
` Okash Khawaja
` Samuel Thibault
` Okash Khawaja [this message]
` Samuel Thibault
` Okash Khawaja
` Gregory Nowak
` Samuel Thibault
` Gregory Nowak
` Janina Sajka
` Tom Fowle
` Janina Sajka
` doubletalks Tom Fowle
` doubletalks Tom Fowle
` doubletalks Janina Sajka
` doubletalks Tom Fowle
` TODO file John Covici
` John Covici
Gregory Nowak
` Tom Fowle
` John Covici
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=20190315105735.41e84bfe@narunkot \
--to=okash.khawaja@gmail.com \
--cc=samuel.thibault@ens-lyon.org \
--cc=speakup@linux-speakup.org \
--cc=w.d.hubbs@gmail.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).