From: Christoph Fritz <chf.fritz@googlemail.com>
To: linux-input@vger.kernel.org
Subject: Re: [PATCH] Support for the eGalax dual-touch panel
Date: Mon, 12 Apr 2010 09:19:55 +0200 [thread overview]
Message-ID: <z2g8f7062ad1004120019g9dbd9069m8b5f9dfcba64f1c9@mail.gmail.com> (raw)
In-Reply-To: <r2l8f7062ad1004120015h21632b7v65deeae98cb1739a@mail.gmail.com>
2010/4/12 Dmitry Torokhov <dmitry.torokhov@gmail.com>:
> On Sat, Apr 10, 2010 at 08:00:59PM +0200, Stéphane Chatty wrote:
>>
>> Le 10 avr. 10 à 18:04, Christoph Fritz a écrit :
>>
>> >Am Samstag, den 10.04.2010, 16:43 +0200 schrieb Stephane Chatty:
>> >>Added support for the eGalax dual-touch panel, found on the Asus
>> >>EeePC T101MT
>> >
>> >>+static void egalax_remove(struct hid_device *hdev)
>> >>+{
>> >>+ hid_hw_stop(hdev);
>> >>+ kfree(hid_get_drvdata(hdev));
>> >>+ hid_set_drvdata(hdev, NULL);
>> >>+}
>> >
>> >Why not using hid_hw_stop() instead of hid_set_drvdata()?
>> >
>
> It is used 2 lines above, isn't it?
sure, that's why I asked (overdetermined)
>
>>
>> Er, actually for a previous driver Dmitry suggested to add this line
>> and I did it without trying to understand :-)
>>
>
> You normally want to reset any pointers you set before, unless core does
> this for you. As far as I know only i2c guys decided to move that into
> core so far.
Should we do this too in a long run?
--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2010-04-12 7:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-10 14:43 [PATCH] Support for the eGalax dual-touch panel Stephane Chatty
2010-04-10 15:48 ` Christoph Fritz
2010-04-10 16:04 ` Christoph Fritz
2010-04-10 18:00 ` Stéphane Chatty
2010-04-10 19:19 ` Jiri Kosina
2010-04-12 3:18 ` Dmitry Torokhov
2010-04-12 6:56 ` Jiri Kosina
2010-04-12 3:21 ` Dmitry Torokhov
[not found] ` <r2l8f7062ad1004120015h21632b7v65deeae98cb1739a@mail.gmail.com>
2010-04-12 7:19 ` Christoph Fritz [this message]
2010-04-10 19:25 ` Jiri Kosina
2010-04-10 19:36 ` Stéphane Chatty
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=z2g8f7062ad1004120019g9dbd9069m8b5f9dfcba64f1c9@mail.gmail.com \
--to=chf.fritz@googlemail.com \
--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).