From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Samuel Thibault <samuel.thibault@ens-lyon.org>
Cc: devel@driverdev.osuosl.org, kirk@reisers.ca,
speakup@linux-speakup.org, linux-kernel@vger.kernel.org,
chris@the-brannons.com
Subject: Re: [patch 0/3] speakup: support 16bit unicode screen reading
Date: Thu, 9 Mar 2017 17:25:51 +0100 [thread overview]
Message-ID: <20170309162551.GA28784@kroah.com> (raw)
In-Reply-To: <20170304140154.421237069@ens-lyon.org>
On Sat, Mar 04, 2017 at 03:01:54PM +0100, Samuel Thibault wrote:
> Hello,
>
> This patch series adds 16bit unicode support to speakup, through three
> patches:
>
> - extend synth buffer to 16bit unicode characters
> - convert screen reading to 16bit characters
> - add unicode variant of /dev/softsynth
This is the second version of this series, correct? Next time, please
put a "v2" in them so that I know which to apply.
thanks,
greg k-h
next prev parent reply other threads:[~2017-03-09 16:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-04 14:01 [patch 0/3] speakup: support 16bit unicode screen reading Samuel Thibault
2017-03-04 14:01 ` [patch 1/3] speakup: extend synth buffer to 16bit unicode characters Samuel Thibault
2017-03-04 14:01 ` [patch 2/3] speakup: convert screen reading to 16bit characters Samuel Thibault
2017-03-04 14:01 ` [patch 3/3] speakup: add unicode variant of /dev/softsynth Samuel Thibault
2017-03-09 16:25 ` Greg Kroah-Hartman [this message]
2017-03-09 16:33 ` [patch 0/3] speakup: support 16bit unicode screen reading Samuel Thibault
-- strict thread matches above, loose matches on Subject: below --
2017-03-02 1:53 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=20170309162551.GA28784@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=chris@the-brannons.com \
--cc=devel@driverdev.osuosl.org \
--cc=kirk@reisers.ca \
--cc=linux-kernel@vger.kernel.org \
--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