From: Chris Brannon <chris@the-brannons.com>
To: speakup@linux-speakup.org
Subject: Re: more fixes for my modded speakup
Date: Sun, 11 Sep 2016 05:40:17 -0700 [thread overview]
Message-ID: <87twdmk3ta.fsf@mushroom.localdomain> (raw)
In-Reply-To: <20160911013834.GA3227@my-p4> (David's message of "Sat, 10 Sep 2016 21:38:34 -0400")
David <david.a.borowski@gmail.com> writes:
> moved bleep into the main with a timer so the catch-up thread only
> handles the synth. then for soft synth, we won't even create it.
Is it safe? If I remember right, I was the one who moved bleep into
its own thread, and I did it because of a kernel change that started
causing lockups. My memory is really fuzzy, and I can't spot anything
in list archives. But maybe it was that kd_mksound was sleeping with a
spinlock held?
-- Chris
prev parent reply other threads:[~ UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
David
` Zachary Kline
` Chris Brannon [this message]
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=87twdmk3ta.fsf@mushroom.localdomain \
--to=chris@the-brannons.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).