From: Rafi Rubin <rafi@seas.upenn.edu>
To: Jiri Kosina <jkosina@suse.cz>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] n-trig digitizer quirks
Date: Wed, 19 Nov 2008 08:42:44 -0500 [thread overview]
Message-ID: <492417D4.4090103@seas.upenn.edu> (raw)
In-Reply-To: <alpine.LNX.1.10.0811191355280.19853@jikos.suse.cz>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
> Could you please keep standard linux-kernel indenting style? I.e.
> something like
Sorry, just had different settings in my vimrc for something else.
>
>
>> +
>> +static int ntrig_input_mapped(struct hid_device *hdev, struct hid_input *hi,
>> + struct hid_field *field, struct hid_usage *usage,
>> + unsigned long **bit, int *max)
>> +{
>> + unsigned long quirks = (unsigned long)hid_get_drvdata(hdev);
>
> This could be removed, as it is never used, right?
Yes, it wasn't used at the moment, just something left over from using hid-lg.c as a template. Since this is the only device known for this driver at this point, is it better to keep it shorter and
not check for the duplicate usage from the driver data or would it be better to add the flexibility now? Also, if you do prefer using driver data like that, is the probe function necessary to make it
work?
Rafi
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAkkkF9IACgkQwuRiAT9o6088RgCfdvu6ntRJ11vh5Ti2CHG+PJJz
SWcAoLrViuX6HO+wEaJnCS+Yt95nAr0D
=qepn
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2008-11-19 13:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-14 17:08 Raphael Yoram Rubin
2008-11-18 14:27 ` Jiri Kosina
2008-11-18 20:44 ` Rafi Rubin
2008-11-19 12:58 ` Jiri Kosina
2008-11-19 13:42 ` Rafi Rubin [this message]
2008-11-19 13:52 ` Jiri Kosina
2008-11-19 14:04 ` Rafi Rubin
2008-11-19 14:07 ` Jiri Kosina
2008-11-19 14:43 ` Rafi Rubin
2008-11-19 15:02 ` Jiri Kosina
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=492417D4.4090103@seas.upenn.edu \
--to=rafi@seas.upenn.edu \
--cc=jkosina@suse.cz \
--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
all inboxes | Powered by JetHome®