From: Greg KH <gregkh@suse.de>
To: "Viktor A. Danilov" <__die@mail.ru>
Cc: linux-kernel@vger.kernel.org, bwheadley@earthlink.net,
chris@crud.net.kroah.org
Subject: Re: PROBLEM: AIPTEK input doesn`t register `device` & `driver` section in sysfs (/sys/class/input/event#)
Date: Tue, 12 Apr 2005 00:41:22 -0700 [thread overview]
Message-ID: <20050412074121.GE1371@kroah.com> (raw)
In-Reply-To: <200504101921.28777.__die@mail.ru>
On Sun, Apr 10, 2005 at 07:21:28PM +0600, Viktor A. Danilov wrote:
>
> PROBLEM: aiptek input doesn`t register `device` & `driver` section in sysfs (/sys/class/input/event#)
> REASON: `dev` - field not filled...
> SOLUTION: in linux/drivers/usb/input/aiptek.c write
> aiptek->inputdev.dev = &intf->dev;
> before calling
> input_register_device(&aiptek->inputdev);
Good catch, I've applied this to my kernel trees.
thanks,
greg k-h
next prev parent reply other threads:[~2005-04-12 7:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-10 13:21 PROBLEM: AIPTEK input doesn`t register `device` & `driver` section in sysfs (/sys/class/input/event#) Viktor A. Danilov
2005-04-12 7:41 ` Greg KH [this message]
2005-06-05 10:21 ` PROBLEM: atiremote " Vincent Vanackere
2005-06-20 15:43 ` Vojtech Pavlik
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=20050412074121.GE1371@kroah.com \
--to=gregkh@suse.de \
--cc=__die@mail.ru \
--cc=bwheadley@earthlink.net \
--cc=chris@crud.net.kroah.org \
--cc=linux-kernel@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