From: Justin Skists <justin.skists@juzza.co.uk>
To: Samuel Thibault <samuel.thibault@ens-lyon.org>,
"Speakup is a screen review system for Linux."
<speakup@linux-speakup.org>,
devel@driverdev.osuosl.org, gregkh@linuxfoundation.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: speakup: refactor synths array to use a list
Date: Wed, 6 Jun 2018 21:28:12 +0100 [thread overview]
Message-ID: <20180606202812.GA25689@tanglefoot> (raw)
In-Reply-To: <20180606132628.fxykchbznrwzgwqt@var.youpi.perso.aquilenet.fr>
[-- Attachment #1: Type: text/plain, Size: 968 bytes --]
On Wed, Jun 06, 2018 at 03:26:28PM +0200, Samuel Thibault wrote:
> Hello,
>
> Justin Skists, le lun. 04 juin 2018 10:52:12 +0100, a ecrit:
> > The synths[] array is a collection of synths acting like a list.
> > There is no need for synths to be an array, so refactor synths[] to use
> > standard kernel list_head API, instead, and modify the usages to suit.
> > As a side-effect, the maximum number of synths has also become redundant.
>
> This looks good to me,
>
> Reviewed-by: Samuel Thibault <samuel.thibault@ens-lyon.org>
Thank you.
> Did you test to e.g. insmod speakup_soft ; insmod speakup_dummy ; rmmod
> speakup_soft ; rmmod speakup_dummy
>
> to make sure it did work correctly?
I did. And I swapped synths via the sysfs interface.
As always, it's always good to double-check. So, I've scripted the test
sequence that I used and attached the output.
> I'd also rather see it tested in the real wild before committing.
As it should be. :)
Justin
[-- Attachment #2: evidence.txt --]
[-- Type: text/plain, Size: 3109 bytes --]
Kernel info
-----------
# uname -a
Linux buildroot 4.17.0-rc7-next-20180601 #1 SMP Mon Jun 4 09:31:05 BST 2018 x86_64 GNU/Linux
insert modules
--------------
# modprobe speakup
# modprobe speakup_dummy dev=ttyS1 ser=1 start=1
# modprobe speakup_soft
# lsmod
Module Size Used by Tainted: G
speakup_soft 16384 0
speakup_dummy 16384 0
speakup 118784 2 speakup_soft,speakup_dummy
switching to soft
-----------------
# echo 'soft' > /sys/accessibility/speakup/synth
# cat /sys/accessibility/speakup/synth
soft
switching to dummy
------------------
# echo 'dummy' > /sys/accessibility/speakup/synth
# cat /sys/accessibility/speakup/synth
dummy
Removing modules
----------------
# rmmod speakup_dummy
# rmmod speakup_soft
# lsmod
Module Size Used by Tainted: G
speakup 118784 0
view message log
----------------
# tail -25 /var/log/messages
Jun 6 20:06:57 buildroot kern.notice kernel: random: ssh-keygen: uninitialized urandom read (32 bytes read)
Jun 6 20:06:57 buildroot kern.notice kernel: random: sshd: uninitialized urandom read (32 bytes read)
Jun 6 20:06:57 buildroot auth.info sshd[105]: Server listening on :: port 22.
Jun 6 20:06:57 buildroot auth.info sshd[105]: Server listening on 0.0.0.0 port 22.
Jun 6 20:06:57 buildroot daemon.info : starting pid 107, tty '/dev/tty1': '/sbin/getty -L tty1 0 vt100 '
Jun 6 20:07:00 buildroot auth.info login[107]: root login on 'tty1'
Jun 6 20:07:08 buildroot kern.notice kernel: random: crng init done
Jun 6 20:07:12 buildroot kern.warn kernel: speakup: module is from the staging directory, the quality is unknown, you have been warned.
Jun 6 20:07:13 buildroot kern.info kernel: input: Speakup as /devices/virtual/input/input4
Jun 6 20:07:13 buildroot kern.info kernel: initialized device: /dev/synth, node (MAJOR 10, MINOR 25)
Jun 6 20:07:13 buildroot kern.info kernel: speakup 3.1.6: initialized
Jun 6 20:07:13 buildroot kern.info kernel: synth name on entry is: (null)
Jun 6 20:07:13 buildroot kern.warn kernel: speakup_dummy: module is from the staging directory, the quality is unknown, you have been warned.
Jun 6 20:07:13 buildroot kern.warn kernel: synth probe
Jun 6 20:07:13 buildroot kern.warn kernel: speakup_soft: module is from the staging directory, the quality is unknown, you have been warned.
Jun 6 20:07:13 buildroot kern.info kernel: releasing synth dummy
Jun 6 20:07:13 buildroot kern.warn kernel: synth probe
Jun 6 20:07:13 buildroot kern.info kernel: initialized device: /dev/softsynth, node (MAJOR 10, MINOR 26)
Jun 6 20:07:13 buildroot kern.info kernel: initialized device: /dev/softsynthu, node (MAJOR 10, MINOR 27)
Jun 6 20:07:13 buildroot kern.warn kernel: soft already in use
Jun 6 20:07:13 buildroot kern.info kernel: releasing synth soft
Jun 6 20:07:13 buildroot kern.info kernel: unregistered /dev/softsynth
Jun 6 20:07:13 buildroot kern.info kernel: unregistered /dev/softsynthu
Jun 6 20:07:13 buildroot kern.warn kernel: synth probe
Jun 6 20:07:13 buildroot kern.info kernel: releasing synth dummy
next prev parent reply other threads:[~2018-06-06 20:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-04 9:52 [PATCH] staging: speakup: refactor synths array to use a list Justin Skists
2018-06-04 9:57 ` Samuel Thibault
2018-06-06 13:26 ` Samuel Thibault
2018-06-06 20:28 ` Justin Skists [this message]
2018-06-11 22:57 ` Samuel Thibault
2018-06-11 23:51 ` Gregory Nowak
2018-06-12 6:31 ` Samuel Thibault
2018-06-18 5:34 ` Gregory Nowak
2018-06-18 6:22 ` Samuel Thibault
2018-06-18 8:41 ` Justin Skists
2018-06-18 8:46 ` Samuel Thibault
2018-06-18 8:55 ` Justin Skists
2018-06-18 8:58 ` Samuel Thibault
2018-06-11 23:55 ` 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=20180606202812.GA25689@tanglefoot \
--to=justin.skists@juzza.co.uk \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--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