From: Johan Hedberg <johan.hedberg@gmail.com>
To: Jeff Hansen <x@jeffhansen.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH] input: Implement idle timeout for fakehid.
Date: Wed, 5 Sep 2012 13:07:18 +0300 [thread overview]
Message-ID: <20120905100718.GC766@x220> (raw)
In-Reply-To: <1346077185-18377-1-git-send-email-x@jeffhansen.com>
Hi Jeff,
On Mon, Aug 27, 2012, Jeff Hansen wrote:
> + fake->timeout = iconn->timeout * 1000;
Why not use the original iconn->timeout value and then use
g_timeout_add_seconds instead of g_timeout_add?
> + guint idle_timeout;
> + uint32_t timeout;
Why uint32_t instead of just int that iconn->timeout is?
> +static gboolean ps3remote_idle(gpointer data)
> +{
> + struct fake_input *fake = data;
> + input_device_request_disconnect(fake->idev);
> + return FALSE;
> +}
Could you add an empty line before and after
input_device_request_disconnect for slightly better readability.
> + if (fake->idle_timeout) {
For consistency with the rest of the code base please use > 0 for
checking for valid GSource IDs. I'd also just call it idle_id to avoid
confusion with "timeout" which is not a GSource ID.
> + g_source_remove(fake->idle_timeout);
> + fake->idle_timeout = 0;
> + }
> + if (fake->timeout)
> + fake->idle_timeout = g_timeout_add(fake->timeout, ps3remote_idle, fake);
Please add an empty line before this second if statement and also do > 0
here.
> + if (fake->idle_timeout) {
And > 0 again here.
Johan
next prev parent reply other threads:[~2012-09-05 10:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-27 14:19 [PATCH] input: Implement idle timeout for fakehid Jeff Hansen
2012-09-05 10:07 ` Johan Hedberg [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-08-17 16:34 Jeff Hansen
2012-08-13 17:40 Jeff Hansen
2012-08-14 9:50 ` Bastien Nocera
2012-08-14 12:51 ` Jeff Hansen
2012-08-01 4:55 Jeff Hansen
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=20120905100718.GC766@x220 \
--to=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=x@jeffhansen.com \
/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).