From: "Michal Malý" <madcatxster@gmail.com>
To: Jiri Kosina <jkosina@suse.cz>
Cc: Simon Wood <simon@mungewell.org>,
linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
Michael Bauer <michael@m-bauer.org>
Subject: Re: [PATCH 1/2] HID: hid-lg4ff: Use Private Data
Date: Tue, 03 Apr 2012 10:02:46 +0200 [thread overview]
Message-ID: <1594934.O1AHdBE0Y7@qosmio-x300> (raw)
In-Reply-To: <alpine.LNX.2.00.1204030413030.16928@pobox.suse.cz>
[-- Attachment #1: Type: text/plain, Size: 1151 bytes --]
On Tuesday 03. of April 2012 4:13:37 you wrote:
> On Mon, 2 Apr 2012, Simon Wood wrote:
> > Use private data in hid-lg4ff to store device properties.
>
> I'd like to have a more verbose changelog -- namely what advantage this
> brings compared to the previous state.
>
> Thanks.
Hi,
the previous implementation used a linked list to store the device
configuration (at this point it was just the operating range, but I have plans
for further expansion, I guess Simon's LEDs patch could use that too).
Searching through the list every time the user adjusted the range wasn't
exactly fast, particularly because the list used kobj name as the ID. I
originally opted for that solution because I didn't want to mess with the code
of the whole hid-lg driver.
This patch takes advantage of the changes introduced in my patches from
2011/04/02. lg4ff now calls hid_get/set_drvdata() to read or store device
configuration. The way I understand it, this is how all HID drivers store their
private data.
Since J. Slabý complained about unnecessary uninitialized_var() macros, I'll
update the patch to remove them.
Michal M.
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 490 bytes --]
next prev parent reply other threads:[~2012-04-03 8:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-31 9:35 [PATCH v4] HID: lg4ff: Remove sysfs iface before deallocating memory Michal Malý
2012-04-02 1:49 ` simon
2012-04-02 14:54 ` [PATCH 1/2] HID: hid-lg4ff: Use Private Data Simon Wood
2012-04-02 14:54 ` [PATCH 2/2] HID: hid-lg4ff: Add support for G27 leds Simon Wood
2012-04-02 16:38 ` Jiri Slaby
2012-04-02 16:32 ` [PATCH 1/2] HID: hid-lg4ff: Use Private Data Jiri Slaby
2012-04-02 17:01 ` simon
2012-04-02 17:30 ` Jiri Slaby
2012-04-03 2:14 ` Jiri Kosina
2012-04-03 2:13 ` Jiri Kosina
2012-04-03 8:02 ` Michal Malý [this message]
2012-04-03 2:12 ` [PATCH v4] HID: lg4ff: Remove sysfs iface before deallocating memory 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=1594934.O1AHdBE0Y7@qosmio-x300 \
--to=madcatxster@gmail.com \
--cc=jkosina@suse.cz \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michael@m-bauer.org \
--cc=simon@mungewell.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).