linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Samuel Thibault <samuel.thibault@ens-lyon.org>
To: speakup@linux-speakup.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Okash Khawaja <okash.khawaja@gmail.com>,
	devel@driverdev.osuosl.org, Kirk Reiser <kirk@reisers.ca>,
	Simon Dickson <simonhdickson@gmail.com>,
	linux-kernel@vger.kernel.org,
	Christopher Brannon <chris@the-brannons.com>
Subject: [HELP REQUESTED from the community] Was: Staging status of speakup
Date: Fri, 12 Jul 2019 11:23:19 +0200	[thread overview]
Message-ID: <20190712092319.wmke4i7zqzr26tly@function> (raw)
In-Reply-To: <20190712083819.GA8862@kroah.com>

Hello,

To readers of the linux-speakup: could you help on this so we can get
Speakup in mainline?  Neither Okash or I completely know what user
consequences the files in /sys/accessibility/speakup/ have, so could
people give brief explanations for each file (something like 3-6 lines
of explanation)?

The i18n/ files have been already documented in section 14.1 of the
spkguide.txt, so we do not need help for them.

Thanks!
Samuel

Greg KH, le ven. 12 juil. 2019 10:38:19 +0200, a ecrit:
> Can you make up a patch to create a
> drivers/staging/speakup/sysfs-speakup file with the needed information?
> That way it will be much easier to determine exactly what these sysfs
> files do and my review can be easier, and perhaps not needed at all :)

  reply	other threads:[~2019-07-12  9:23 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-15 13:01 Staging status of speakup Okash Khawaja
2019-03-16  1:19 ` Chris Brannon
2019-03-16  9:35   ` Samuel Thibault
2019-03-16 10:22     ` Samuel Thibault
2019-03-19 16:31     ` Alan Cox
2019-03-19 17:07       ` Samuel Thibault
2019-03-19 17:11       ` Adam Borowski
2019-03-20 20:54       ` Okash Khawaja
2019-03-16 10:05   ` Okash Khawaja
2019-03-16  3:18 ` Greg Kroah-Hartman
2019-03-16 10:09   ` Okash Khawaja
2019-07-06 19:08   ` Okash Khawaja
2019-07-07  6:57     ` Greg Kroah-Hartman
2019-07-12  8:38       ` Greg Kroah-Hartman
2019-07-12  9:23         ` Samuel Thibault [this message]
2019-07-13  0:46           ` [HELP REQUESTED from the community] Was: " Gregory Nowak
2019-07-25  3:53             ` Gregory Nowak
2019-07-25  4:04               ` Chris Brannon
2019-07-25 10:44                 ` John Covici
2019-08-21 16:39                   ` Okash Khawaja
2019-08-21 22:22                     ` Gregory Nowak
2019-09-08  9:43                       ` Okash Khawaja
2019-09-09  2:54                         ` Gregory Nowak
2019-09-14 21:08                           ` Okash Khawaja
2019-09-14 23:32                             ` Samuel Thibault
2019-09-15 13:43                             ` Greg Kroah-Hartman
2019-09-15 18:41                               ` Okash Khawaja
2019-09-16 13:47                                 ` Samuel Thibault
2019-09-16 14:11                                   ` Greg Kroah-Hartman
2019-09-16 22:38                                     ` Gregory Nowak
2019-09-17  8:01                                       ` Greg Kroah-Hartman
2019-09-18  1:03                                         ` Gregory Nowak
2019-09-18  6:16                                           ` Greg Kroah-Hartman
2019-09-18 20:30                                             ` Gregory Nowak
2019-09-20  7:46                                               ` Greg Kroah-Hartman
2019-09-20 10:18                                                 ` Okash Khawaja
2019-09-16 20:21                                   ` Gregory Nowak
2019-07-25  6:11               ` Willem van der Walt
2019-07-25  6:33                 ` Greg Kroah-Hartman
2019-07-25 10:41               ` John Covici
2019-07-12  9:24         ` 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=20190712092319.wmke4i7zqzr26tly@function \
    --to=samuel.thibault@ens-lyon.org \
    --cc=chris@the-brannons.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=kirk@reisers.ca \
    --cc=linux-kernel@vger.kernel.org \
    --cc=okash.khawaja@gmail.com \
    --cc=simonhdickson@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 NNTP newsgroup(s).