From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Christopher Hudson <chris.hudson.comp.eng@gmail.com>
Cc: linux-input@vger.kernel.org, Chris Hudson <chudson@kionix.com>
Subject: Re: [PATCH RESEND] input: kxtj9: who_am_i check value and initial data rate fixes
Date: Sat, 17 Mar 2012 21:19:39 -0700 [thread overview]
Message-ID: <20120318041939.GB19118@core.coreip.homeip.net> (raw)
In-Reply-To: <CAB7Re7UT7tULwGqcwn+iQRC+nciDUS4J8LSVP5NasK3p1SOfsw@mail.gmail.com>
Hi Christopher,
On Fri, Mar 16, 2012 at 02:53:33PM -0400, Christopher Hudson wrote:
> ---------- Forwarded message ----------
> From: <chris.hudson.comp.eng@gmail.com>
> Date: Fri, Feb 3, 2012 at 10:27 AM
> Subject: [PATCH 1/1] input: kxtj9: who_am_i check value and initial data
> rate fixes
> To: linux-input@vger.kernel.org
> Cc: dmitry.torokhov@gmail.com, chris.hudson.comp.eng@gmail.com, Chris
> Hudson <chudson@kionix.com>
>
> From: Chris Hudson <chudson@kionix.com>
>
> Several fixes based on customer feedback:
> - WHO_AM_I value has changed since preliminary parts used for initial
> testing
> - Output of le16_to_cpu must be saved to memory before shifting to preserve
> sign
> - Initial data rate was not extracted from data control register init.
> This was
> causing the initial data rate to be set to maximum until it was changed.
> To
> fix this problem, it made more sense to specify an initial data rate and
> extract the register mask from that.
>
> Signed-off-by: Chris Hudson <chudson@kionix.com>
Your mailer messed up the patch (tabs converted to spaces, lines wrapped
up). I fixed it up and applied but please use proper MTA next time
around.
Thanks.
--
Dmitry
prev parent reply other threads:[~2012-03-18 4:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-03 15:27 [PATCH 1/1] input: kxtj9: who_am_i check value and initial data rate fixes Chris, Hudson
[not found] ` <CAB7Re7UT7tULwGqcwn+iQRC+nciDUS4J8LSVP5NasK3p1SOfsw@mail.gmail.com>
2012-03-18 4:19 ` Dmitry Torokhov [this message]
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=20120318041939.GB19118@core.coreip.homeip.net \
--to=dmitry.torokhov@gmail.com \
--cc=chris.hudson.comp.eng@gmail.com \
--cc=chudson@kionix.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).