From: Alessandro Rubini <rubini@unipv.it>
To: jrnieder@gmail.com
Cc: gjthill@gmail.com, dmitry.torokhov@gmail.com,
linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
607242@bugs.debian.org
Subject: Re: [PATCH v2] psmouse: mitigate failing-mouse symptoms
Date: Sun, 30 Sep 2012 20:02:40 +0200 [thread overview]
Message-ID: <20120930180240.GA31164@mail.gnudd.com> (raw)
In-Reply-To: <20120930174353.GA29129@elie.Belkin>
> I think this would be less controversial if the run-time default were
> to disable the feature.
Yes, that's the common sensible path to new little-tested features.
As you say, it may become enabled by default over time.
Then, I think it would be good to have a specific sub-structure for
this stuff. It would allow this:
+ psmouse->err_log_base = 0;
+ psmouse->interval_base = 0;
+ psmouse->hotio_log_base = 0;
+ psmouse->err_log_counter = 0;
+ psmouse->interval_pkts = 0;
+ psmouse->hotio_log_counter = 0;
to be replaced with a memset. I also think it would make it clearer
what these are:
+ unsigned long interval_base;
+ unsigned long interval_pkts;
+ unsigned long hotio_log_base;
+ unsigned long hotio_log_counter;
+ unsigned long err_log_base;
+ unsigned long err_log_counter;
to the casual reader.
This is only a suggestion, though.
thanks
/alessandro
next prev parent reply other threads:[~2012-09-30 18:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-09 22:00 [PATCH v2] psmouse: mitigate failing-mouse symptoms Jim Hill
2012-09-30 17:43 ` Jonathan Nieder
2012-09-30 18:02 ` Alessandro Rubini [this message]
2012-10-03 5:19 ` Jim Hill
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=20120930180240.GA31164@mail.gnudd.com \
--to=rubini@unipv.it \
--cc=607242@bugs.debian.org \
--cc=dmitry.torokhov@gmail.com \
--cc=gjthill@gmail.com \
--cc=jrnieder@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@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).