From: Okash Khawaja <okash.khawaja@gmail.com>
To: Samuel Thibault <samuel.thibault@ens-lyon.org>
Cc: speakup@linux-speakup.org
Subject: Re: staging: speakup: add send_xchar, tiocmset and input functionality for tty
Date: Sat, 29 Apr 2017 14:28:01 +0100 [thread overview]
Message-ID: <20170429132801.GA1181@sanghar> (raw)
In-Reply-To: <20170429120745.fpyk5ixwa2khhtyj@var.youpi.perso.aquilenet.fr>
Hi,
On Sat, Apr 29, 2017 at 02:07:45PM +0200, Samuel Thibault wrote:
> Okash Khawaja, on sam. 29 avril 2017 09:47:23 +0100, wrote:
> > On Fri, Apr 28, 2017 at 11:23:58PM +0200, Samuel Thibault wrote:
> >
> > > So I guess now we need to be more pushy with serdev.
> > Haven't heard from Rob Herring yet. What do you suggest?
>
> I'd say assume that it's fine, and work on writing a patch that works,
> for more concrete discussion, and possibly mere integration by gkh
> without going through Rob.
Sounds good! We have all the patches. Apart from the patch you are
reviewing in this thread there is
http://linux-speakup.org/pipermail/speakup/2017-April/060645.html
which is not yet signed off (we haven't had feedback on decext).
I will now get latest staging-next from kernel source, just to be sure
that patches all apply cleanly.
Do you want me to post all of them here as one patch set? Because since
I last posted, one of them has been upstreamed.
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
[patch 0/7] staging: speakup: migrate synths to use TTY-based comms Okash Khawaja
` [patch 1/7] staging: speakup: add send_xchar and tiocmset methods Okash Khawaja
` Okash Khawaja
` [patch 2/7] staging: speakup: make input functionality swappable Okash Khawaja
` Samuel Thibault
` [patch 3/7] tty: export tty_open_by_driver Okash Khawaja
` [patch 4/7] staging: speakup: add tty-based comms functions Okash Khawaja
` [patch 5/7] staging: speakup: migrate acntsa, bns, dummy and txprt to ttyio Okash Khawaja
` [patch 6/7] staging: speakup: add send_xchar, tiocmset and input functionality for tty Okash Khawaja
` Samuel Thibault
` Okash Khawaja
` Okash Khawaja
` Samuel Thibault
` Okash Khawaja
` Rob
` Okash Khawaja
` Samuel Thibault
` Okash Khawaja
` Samuel Thibault
` Okash Khawaja
` Okash Khawaja
` Samuel Thibault
` Okash Khawaja
` Samuel Thibault
` Okash Khawaja [this message]
` Samuel Thibault
` [patch 7/7] staging: speakup: migrate apollo, ltlk, audptr, decext, dectlk and spkout Okash Khawaja
` [patch 0/7] staging: speakup: migrate synths to use TTY-based comms 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=20170429132801.GA1181@sanghar \
--to=okash.khawaja@gmail.com \
--cc=samuel.thibault@ens-lyon.org \
--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).