public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Bastien Nocera <hadess@hadess.net>
To: "Ruslan N. Marchenko" <rufferson@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH] PS3Remote unpairing and power-saving
Date: Fri, 18 Sep 2009 14:49:26 +0100	[thread overview]
Message-ID: <1253281766.18963.4279.camel@localhost.localdomain> (raw)
In-Reply-To: <a70b8cd30909180631r4546ffc0q66edc6cc8bd010f2@mail.gmail.com>

On Fri, 2009-09-18 at 15:31 +0200, Ruslan N. Marchenko wrote:
> Hi Bastien,
> 
> Thanks for finding your time for review.
> 
> 2009/9/18, Bastien Nocera <hadess@hadess.net>:
> > Don't use statics, add those to a ps3 specific struct.
> 
> This function is ps3remote_event which supposed to be use for ps3remote only,
> also the driver assumes only single ps3remote device per bluez instance.
> I just copied semantic from ps3remote_decode function, where also 2
> statics are used. Though I can move them all to input structure.
> Should I?

Please. And if you manage to make it handle more than one remote in the
process, then all the better.

> > > +     g_timer_start(((struct fake_hid *)fake->priv)->timer);
> >
> >
> > Why do you start the timer unconditionally, instead of just when using
> >  the HOME key?
> >
> 
> Because this statement is to reset event timer, which causes remote to
> be disconnected on idle. Each key-press resets the timer
> unconditionally. g_timer_start is recommended to use instead of
> g_timer_reset since they do the same thing and reset will be
> deprecated (I guess).

Looks fine.

Cheers


  reply	other threads:[~2009-09-18 13:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-28 14:42 [PATCH] PS3Remote unpairing and power-saving Ruslan N. Marchenko
2009-09-09  9:06 ` Ruslan N. Marchenko
2009-09-18 11:10 ` Bastien Nocera
2009-09-18 13:31   ` Ruslan N. Marchenko
2009-09-18 13:49     ` Bastien Nocera [this message]
2009-09-23 18:14       ` Ruslan N. Marchenko

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=1253281766.18963.4279.camel@localhost.localdomain \
    --to=hadess@hadess.net \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=rufferson@gmail.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