public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: Okash Khawaja <okash.khawaja@gmail.com>
To: speakup@linux-speakup.org
Subject: Re: [patch 0/8] staging: speakup: introduce tty-based comms
Date: Sun, 12 Mar 2017 12:23:58 +0000	[thread overview]
Message-ID: <20170312122358.GA4239@sanghar> (raw)
In-Reply-To: <20170312121644.448468179@gmail.com>

Couple of typos corrected below..

On Sun, Mar 12, 2017 at 12:16:44PM +0000, okash.khawaja@gmail.com wrote:
> Hi,                                                                                                                                                                                                                 
> 
> This patchset introduces a TTY-based way for the synths to communicate
> with devices as an alternate for direct serial comms used by the synths
> at the moment. It then migrates some of the synths to the TTY-based
> comms. Synths migrated in this patchset are dummy, acntsa, bns and
> txprt.
> 
> The last patch also migrates ltlk with some temporary modification which
> means that initial info from synth won't be retried. This shouldn't affect

means that initial info from synth won't be retrieved**.

> normal functionality of the synth. We won't be sending lkml migration

We won't be sending ltlk** migration

> to LKML, however it will be good to test it here.
> 
> I have also added the "TODO: support more than ttyS*" next to MKDEV line in
> spk_ttyio.c, which was discussed last time but I hadn't put in.
> 
> Finally, please note that these apply cleanly on top of the latest staging
> tree, which includes unicode changes recently merged.
> 
> Thanks,
> Okash

  reply	other threads:[~ UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 okash.khawaja
 ` Okash Khawaja [this message]
 ` John Covici
   ` Samuel Thibault
 ` Samuel Thibault
   ` Okash Khawaja
     ` Samuel Thibault
       ` Okash Khawaja

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=20170312122358.GA4239@sanghar \
    --to=okash.khawaja@gmail.com \
    --cc=speakup@linux-speakup.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 read-only IMAP folder(s) and NNTP newsgroup(s).