From: Pete Zaitcev <zaitcev@redhat.com>
To: Ping Cheng <pingc@wacom.com>
Cc: linux-kernel@vger.kernel.org, vojtech@suse.cz
Subject: Re: Wacom USB driver patch
Date: Wed, 11 Feb 2004 11:04:39 -0800 [thread overview]
Message-ID: <20040211110439.1a64fe9b.zaitcev@redhat.com> (raw)
In-Reply-To: <mailman.1076463721.27289.linux-kernel2news@redhat.com>
On Tue, 10 Feb 2004 17:23:11 -0800
Ping Cheng <pingc@wacom.com> wrote:
> <<linuxwacom.patch>>
This looks much better, it's not line-wrapped.
I have one question though, about this part:
@@ -152,15 +150,103 @@ static void wacom_pl_irq(struct urb *urb
+ /* was entered with stylus2 pressed */
+ if (wacom->tool[1] == BTN_TOOL_RUBBER && !(data[4] & 0x20) ) {
+ /* report out proximity for previous tool */
+ input_report_key(dev, wacom->tool[1], 0);
+ input_sync(dev);
+ wacom->tool[1] = BTN_TOOL_PEN;
+ return;
+ }
Is it safe to just return without resubmitting the urb here?
@@ -231,8 +317,12 @@ static void wacom_graphire_irq(struct ur
+ /* check if we can handle the data */
+ if (data[0] == 99)
+ return;
+
if (data[0] != 2)
Same here.
Also, please add the path to the patch, e.g. always use recursive diff.
-- Pete
next parent reply other threads:[~2004-02-11 19:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1076463721.27289.linux-kernel2news@redhat.com>
2004-02-11 19:04 ` Pete Zaitcev [this message]
2004-03-17 22:24 Wacom USB driver patch Ping Cheng
[not found] <Pine.LNX.4.58L.0402262354190.1653@logos.cnet>
2004-03-17 17:29 ` Pete Zaitcev
2004-03-17 20:36 ` Vojtech Pavlik
-- strict thread matches above, loose matches on Subject: below --
2004-02-20 22:29 Ping Cheng
2004-02-13 0:55 Ping Cheng
2004-02-13 3:28 ` Pete Zaitcev
2004-02-13 8:13 ` Vojtech Pavlik
2004-02-11 19:47 Ping Cheng
2004-02-11 20:04 ` Vojtech Pavlik
2004-02-11 1:23 Ping Cheng
2004-02-11 8:24 ` Vojtech Pavlik
2004-03-08 9:05 ` Vojtech Pavlik
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=20040211110439.1a64fe9b.zaitcev@redhat.com \
--to=zaitcev@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pingc@wacom.com \
--cc=vojtech@suse.cz \
/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