From: Erik Slagter <erik@slagter.name>
To: Jiri Kosina <jikos@jikos.cz>
Cc: linux-input@vger.kernel.org
Subject: Re: event devices not released
Date: Tue, 12 Feb 2008 12:44:49 +0100 [thread overview]
Message-ID: <47B186B1.7020306@slagter.name> (raw)
In-Reply-To: <Pine.LNX.4.64.0802121151010.7699@twin.jikos.cz>
[-- Attachment #1: Type: text/plain, Size: 471 bytes --]
Jiri Kosina wrote:
> That is OK. But you shouldn't run into the situation when you run out of
> the free evdev devices.
Seems indeed to be a misinterpretation on my side.
I add a few debug statements, and it seems that although the event
device kernel name increases, they still reference the same event device
slot(s). Also I don't get the "out of event devices" error now, even
with hald running. I'll check shortly whether this also counts for
suspend cycles.
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 3315 bytes --]
prev parent reply other threads:[~2008-02-12 11:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-11 12:47 event devices not released Erik Slagter
2008-02-11 16:58 ` Dmitry Torokhov
2008-02-11 20:15 ` Erik Slagter
2008-02-11 21:48 ` Jiri Kosina
2008-02-12 9:10 ` Erik Slagter
2008-02-12 10:51 ` Jiri Kosina
2008-02-12 11:27 ` Erik Slagter
2008-02-12 11:44 ` Erik Slagter [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=47B186B1.7020306@slagter.name \
--to=erik@slagter.name \
--cc=jikos@jikos.cz \
--cc=linux-input@vger.kernel.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).