From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Henrik Rydberg <rydberg@euromail.se>
Cc: "Éric Piel" <E.A.B.Piel@tudelft.nl>,
"Florian Ragwitz" <rafl@debian.org>,
"linux-input@vger.kernel.org" <linux-input@vger.kernel.org>
Subject: Re: [PATCH 2/2 v3] elantech: Report multitouch with proper ABS_MT messages
Date: Mon, 10 May 2010 17:11:21 -0700 [thread overview]
Message-ID: <20100511001121.GB21081@core.coreip.homeip.net> (raw)
In-Reply-To: <4BE89DB3.1050206@euromail.se>
On Tue, May 11, 2010 at 01:58:43AM +0200, Henrik Rydberg wrote:
> Éric Piel wrote:
> > Op 10-05-10 22:53, Henrik Rydberg schreef:
> >> Hi again Éric,
> >>
> >> thanks for your changes, the first patch looks better now. However, both patches
> >> still have style problems. Also, the second patch now makes unrelated changes to
> >> the ABS_X etc, so it is difficult to even know what was tested, and whether the
> >> first patch really works as claimed.
> > What are the style problems of the first patch? I tried to fix all of them.
>
> WARNING: line over 80 characters
> #212: FILE: drivers/input/mouse/elantech.c:483:
> + input_set_abs_params(dev, ABS_TOOL_WIDTH, ETP_WMIN_V2, ETP_WMAX_V2, 0, 0);
>
> WARNING: line over 80 characters
> #119: FILE: drivers/input/mouse/elantech.c:498:
> + input_set_abs_params(dev, ABS_MT_POSITION_X, ETP_XMIN_V2, ETP_XMAX_V2, 0, 0);
>
> WARNING: line over 80 characters
> #120: FILE: drivers/input/mouse/elantech.c:499:
> + input_set_abs_params(dev, ABS_MT_POSITION_Y, ETP_YMIN_V2, ETP_YMAX_V2, 0, 0);
>
Do not worry about the 80 char limit that much, especially if it
produces less readable code due to wierd line splits. The code above
could be broken cleanly, but it's not a big deal.
The rest of the checkpatch warnirngs (if any) I prefer to have
addressed though.
> >
> > Concerning the second patch, it's necessary to change the lines with
> > ABS_X, because otherwise the computation would be duplicated for the MT
> > part and it would make everything look more complicated. Honestly, I
> > think this change is still very limited and can easily be reviewed for
> > not changing the semantic.
>
> Yes, you are right about x1 and y1. The patch patch touches the width variable
> for no apparent reason, and I stopped reading there.
>
> If this process seems trivial and tedious to you, consider how it must appear to
> those who deal with patches every day. Most people will not even look at a patch
> with style problems, so the real review _starts_ when those issues are fixed.
>
> Henrik
--
Dmitry
--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2010-05-11 0:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-08 16:39 [PATCH 2/2 v2] elantech: Report multitouch with proper ABS_MT messages Éric Piel
2010-05-10 20:11 ` [PATCH 2/2 v3] " Éric Piel
2010-05-10 20:53 ` Henrik Rydberg
2010-05-10 22:27 ` Éric Piel
2010-05-10 23:58 ` Henrik Rydberg
2010-05-11 0:11 ` Dmitry Torokhov [this message]
2010-05-11 0:48 ` Henrik Rydberg
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=20100511001121.GB21081@core.coreip.homeip.net \
--to=dmitry.torokhov@gmail.com \
--cc=E.A.B.Piel@tudelft.nl \
--cc=linux-input@vger.kernel.org \
--cc=rafl@debian.org \
--cc=rydberg@euromail.se \
/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).