From: Matteo Delfino <kendatsuba@gmail.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: linux-input@vger.kernel.org, Alessandro Rubini <rubini@ipvvis.unipv.it>
Subject: Re: [PATCH] elantech: fix for newer hardware versions (v7)
Date: Sat, 06 Jul 2013 09:20:34 +0200 [thread overview]
Message-ID: <51D7C542.6040705@gmail.com> (raw)
In-Reply-To: <20130706043029.GA8212@core.coreip.homeip.net>
Hi Dmitry,
On 07/06/2013 06:30 AM, Dmitry Torokhov wrote:
> Thank you for the patch, unfortunately your mailer line-wrapped it and
> it can't be applied. Could you please resend it using MUA that does not
> perform line-wrapping?
>
Of course, sorry about that.
> Also, now that you only use (packet[3] & 0x03) to determine packet type,
> could you turn series of 'if' statements in elantech_packet_check_v4()
> into a 'switch'?
Sure, i will.
Best regards,
Matteo
prev parent reply other threads:[~2013-07-06 7:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-05 22:18 [PATCH] elantech: fix for newer hardware versions (v7) Matteo Delfino
2013-07-06 4:30 ` Dmitry Torokhov
2013-07-06 7:20 ` Matteo Delfino [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=51D7C542.6040705@gmail.com \
--to=kendatsuba@gmail.com \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=rubini@ipvvis.unipv.it \
/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).