From: Henrik Rydberg <rydberg@bitmath.org>
To: Matt Whitlock <linux@mattwhitlock.name>,
linux-input@vger.kernel.org,
Dmitry Torokhov <dmitry.torokhov@gmail.com>
Subject: Re: [PATCH 2/2] Input: bcm5974 - report ABS_MT_PRESSURE + remove redundant emulation code
Date: Mon, 6 Jul 2015 21:11:06 +0200 [thread overview]
Message-ID: <559AD2CA.7000804@bitmath.org> (raw)
In-Reply-To: <7271343.oGOpcDThz2@crushinator>
Hi Matt,
> It's been four weeks, and I haven't heard back on this patch. I believe I've
> implemented what was requested. Is there a problem with it?
I thought you did get response on this patch set, concerning the fabrication of
force data? I seem to remember a mail from Dmitry about this, although I cannot
find it now.
I think your patch is a good reduction, all in accord with what we talked about,
but I have doubts that it will not create regressions. From what I have seen so
far, patch-wise, the best solution is to leave the code as it is.
I understand that the constraints now seem to depict the empty set, but maybe
there is a third solution.
Henrik
next prev parent reply other threads:[~2015-07-06 19:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-03 11:49 [PATCH] Input: bcm5974 - report highest finger pressure to Synaptics Matt Whitlock
2015-06-03 12:24 ` Henrik Rydberg
2015-06-03 12:31 ` Matt Whitlock
2015-06-03 12:52 ` Henrik Rydberg
2015-06-09 1:07 ` [PATCH 1/2] Input: input_mt_report_pointer_emulation(), rescale pressure + tool width Matt Whitlock
2015-06-09 1:07 ` [PATCH 2/2] Input: bcm5974 - report ABS_MT_PRESSURE + remove redundant emulation code Matt Whitlock
2015-07-06 18:37 ` Matt Whitlock
2015-07-06 19:11 ` Henrik Rydberg [this message]
2015-07-06 19:35 ` Matt Whitlock
2015-07-06 19:44 ` Henrik Rydberg
2015-07-06 19:59 ` Matt Whitlock
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=559AD2CA.7000804@bitmath.org \
--to=rydberg@bitmath.org \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux@mattwhitlock.name \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.