From: Jean Delvare <khali@linux-fr.org>
To: linux-input@atrey.karlin.mff.cuni.cz,
Dmitry Torokhov <dmitry.torokhov@gmail.com>
Subject: Ever-increasing serio device number
Date: Thu, 21 Jun 2007 23:00:40 +0200 [thread overview]
Message-ID: <20070621230040.79fe959d@hyperion.delvare> (raw)
Hi Dmitry, hi all,
While developing my i2c-taos-evm driver [1], I noticed that my device
was getting a new serio device number each time I cycled my driver. It
started as serio2, and after an afternoon of testing, it was serio19.
I'm curious, is this intended? I expected freed numbers to be reused,
as i2c does.
If this isn't supposed to happen, would this be a bug in the serio
driver, or in my driver (maybe not releasing some resource properly)?
Thanks.
[1] http://lists.lm-sensors.org/pipermail/i2c/2007-June/001508.html
--
Jean Delvare
next reply other threads:[~2007-06-21 21:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-21 21:00 Jean Delvare [this message]
2007-06-22 19:30 ` Ever-increasing serio device number Dmitry Torokhov
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=20070621230040.79fe959d@hyperion.delvare \
--to=khali@linux-fr.org \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@atrey.karlin.mff.cuni.cz \
/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).