From: Jiri Kosina <jkosina@suse.cz>
To: Elias Vanderstuyft <elias.vds@gmail.com>,
Simon Wood <simon@mungewell.org>
Cc: linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
"Michal Malý" <madcatxster@prifuk.cz>
Subject: Re: [PATCHv2 3/3] HID:Kconfig: Correct MOMO description in wrong place (handled by LG4FF).
Date: Mon, 14 Oct 2013 16:03:35 +0200 (CEST) [thread overview]
Message-ID: <alpine.LNX.2.00.1310141602540.12405@pobox.suse.cz> (raw)
In-Reply-To: <CADbOyBQodqzSb04OCO6oduJSZvveZXxQjSdp+CdyKKk5Bs=O7w@mail.gmail.com>
On Thu, 10 Oct 2013, Elias Vanderstuyft wrote:
> I don't see any report-descriptor being fixed up, this results in having
> only two axes: steering and combined accel-brake axis.
> So, same procedure as the Formula Vibration wheel, I'll send you the report
> descriptor and some hidraw data when using the accel and brake pedals, in
> my next mail.
So should I wait for v3, where the rdesc fixup for splitting the axes will
be done, or are you planning to submit it to me as a followup patch?
--
Jiri Kosina
SUSE Labs
next prev parent reply other threads:[~2013-10-14 14:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-10 0:04 [PATCH 1/3] HID:hid-lg: Fixed ReportDescriptor for Logitech Formular Vibration to split Accel/Brake into seperate axis Simon Wood
2013-10-10 0:04 ` [PATCH 2/3] HID:hid-lg: Fixed Report Descriptor for Logitech MOMO Force (Black) " Simon Wood
2013-10-10 8:02 ` Jiri Kosina
2013-10-10 14:20 ` [PATCHv2 1/3] HID:hid-lg: Fixed ReportDescriptor for Logitech Formula Vibration " Simon Wood
2013-10-10 14:20 ` [PATCHv2 2/3] HID:hid-lg: Fixed Report Descriptor for Logitech MOMO Force (Black) " Simon Wood
2013-10-10 14:20 ` [PATCHv2 3/3] HID:Kconfig: Correct MOMO description in wrong place (handled by LG4FF) Simon Wood
[not found] ` <CADbOyBQodqzSb04OCO6oduJSZvveZXxQjSdp+CdyKKk5Bs=O7w@mail.gmail.com>
2013-10-14 14:03 ` Jiri Kosina [this message]
2013-10-14 14:58 ` simon
2013-10-14 18:48 ` Jiri Kosina
2013-10-10 0:04 ` [PATCH " Simon Wood
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=alpine.LNX.2.00.1310141602540.12405@pobox.suse.cz \
--to=jkosina@suse.cz \
--cc=elias.vds@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=madcatxster@prifuk.cz \
--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
all inboxes | Powered by JetHome®