linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Anderson Lizardo <anderson.lizardo@openbossa.org>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH] Bluetooth: Update MGMT and SMP timeout constants to use msecs_to_jiffies
Date: Thu, 01 Mar 2012 16:48:39 -0800	[thread overview]
Message-ID: <1330649319.3392.110.camel@aeonflux> (raw)
In-Reply-To: <CAJdJm_PHQOfstiuUfMfgtceWN=Ko37COLQNKkXb12Gc3CEOchw@mail.gmail.com>

Hi Anderson,

> > The MGMT and SMP timeout constants are always used in form of jiffies. So
> > just include the conversion from msecs in the define itself. This has the
> > advantage of making the code where the timeout is used more readable.
> >
> > Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
> > ---
> >  net/bluetooth/mgmt.c |    5 ++---
> >  net/bluetooth/smp.c  |    5 ++---
> >  2 files changed, 4 insertions(+), 6 deletions(-)
> >
> > diff --git a/net/bluetooth/mgmt.c b/net/bluetooth/mgmt.c
> > index 7bd7d57..40b3da3 100644
> > --- a/net/bluetooth/mgmt.c
> > +++ b/net/bluetooth/mgmt.c
> > @@ -116,7 +116,7 @@ static const u16 mgmt_events[] = {
> >  #define INQUIRY_LEN_BREDR              0x08    /* TGAP(100) */
> >  #define INQUIRY_LEN_BREDR_LE           0x04    /* TGAP(100)/2 */
> >
> > -#define SERVICE_CACHE_TIMEOUT (5 * 1000)
> > +#define CACHE_TIMEOUT  msecs_to_jiffies(2 * 1000)
> 
> Was it intentional to change timeout from 5 seconds to 2 seconds on this commit?

the change was intentional, but unintentional I forgot to mention it in
the commit message.

Regards

Marcel
 


      reply	other threads:[~2012-03-02  0:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-01 22:32 [PATCH] Bluetooth: Update MGMT and SMP timeout constants to use msecs_to_jiffies Marcel Holtmann
2012-03-01 22:36 ` Johan Hedberg
2012-03-02  0:23 ` Anderson Lizardo
2012-03-02  0:48   ` Marcel Holtmann [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=1330649319.3392.110.camel@aeonflux \
    --to=marcel@holtmann.org \
    --cc=anderson.lizardo@openbossa.org \
    --cc=linux-bluetooth@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).