From: "Dmitry Torokhov" <dmitry.torokhov@gmail.com>
To: "Andrew Morton" <akpm@osdl.org>
Cc: "Burman Yan" <yan_952@hotmail.com>,
linux-kernel@vger.kernel.org, "Jean Delvare" <khali@linux-fr.org>
Subject: Re: [PATCH] HP Mobile data protection system driver with interrupt handling
Date: Mon, 6 Nov 2006 17:18:53 -0500 [thread overview]
Message-ID: <d120d5000611061418i65f27cd6w1c60692aff8bd1b1@mail.gmail.com> (raw)
In-Reply-To: <20061106131535.04ffa895.akpm@osdl.org>
On 11/6/06, Andrew Morton <akpm@osdl.org> wrote:
> On Fri, 03 Nov 2006 18:33:31 +0200
> "Burman Yan" <yan_952@hotmail.com> wrote:
> > +
> > +static unsigned int mouse = 0;
>
> The `= 0' is unneeded.
>
> > +module_param(mouse, bool, S_IRUGO);
> > +MODULE_PARM_DESC(mouse, "Enable the input class device on module load");
Does the parameter have to be called "mouse"? I'd rename it to "input"
and drop the work "class" from parameter description.
> > +
> > + if (input_register_device(mdps.idev)) {
> > + input_free_device(mdps.idev);
> > + mdps.idev = NULL;
> > + return;
> > + }
> > +
> > + mdps.kthread = kthread_run(mdps_mouse_kthread, NULL, "kmdps");
> > + if (IS_ERR(mdps.kthread)) {
> > + input_unregister_device(mdps.idev);
> > + mdps.idev = NULL;
> > + return;
> > + }
> > +
Please consider implementing mdps_input_open() and mdps_input_close()
and create and run the polling thread from there - there is no point
in polling the device if noone listens to its events.
--
Dmitry
next prev parent reply other threads:[~2006-11-06 22:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-03 16:33 Burman Yan
2006-11-06 21:15 ` Andrew Morton
2006-11-06 22:18 ` Dmitry Torokhov [this message]
2006-11-07 19:19 ` Burman Yan
2006-11-07 20:37 ` Dmitry Torokhov
2006-11-08 5:16 ` Burman Yan
2006-11-07 19:09 ` Burman Yan
2006-11-07 7:03 ` Pavel Machek
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=d120d5000611061418i65f27cd6w1c60692aff8bd1b1@mail.gmail.com \
--to=dmitry.torokhov@gmail.com \
--cc=akpm@osdl.org \
--cc=khali@linux-fr.org \
--cc=linux-kernel@vger.kernel.org \
--cc=yan_952@hotmail.com \
/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
all inboxes | Powered by JetHome®