public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrei Emeltchenko <Andrei.Emeltchenko.news@gmail.com>
To: Anderson Lizardo <anderson.lizardo@openbossa.org>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH] Bluetooth: Use AUTO_OFF constant in jiffies
Date: Thu, 14 Jun 2012 17:22:16 +0300	[thread overview]
Message-ID: <20120614142214.GA2585@aemeltch-MOBL1> (raw)
In-Reply-To: <CAJdJm_MtZYC9=nFzchcCR+yZiyGVNCMpXnmPf7D-dKut1UT8BA@mail.gmail.com>

Hi Anderson,

On Thu, Jun 14, 2012 at 08:07:40AM -0400, Anderson Lizardo wrote:
> > Move AUTO_OFF_TIMEOUT to other constants changing name to
> > HCI_AUTO_OFF_TIMEOUT and convert to jiffies.
> >
> > Signed-off-by: Andrei Emeltchenko <andrei.emeltchenko@intel.com>
> > ---
> >  include/net/bluetooth/hci.h |    3 ++-
> >  net/bluetooth/hci_core.c    |    5 +----
> >  2 files changed, 3 insertions(+), 5 deletions(-)
> >
> > diff --git a/include/net/bluetooth/hci.h b/include/net/bluetooth/hci.h
> > index 3d1ad2c..a7b334e 100644
> > --- a/include/net/bluetooth/hci.h
> > +++ b/include/net/bluetooth/hci.h
> > @@ -153,8 +153,9 @@ enum {
> >  #define HCI_DISCONN_TIMEOUT    msecs_to_jiffies(4000)  /* 2 seconds */
> 
> There is a typo in the comment above. It should be "4 seconds". Maybe
> you can fix it in a separate patch together with the "seconds" ->
> "second" fix you did below?

Sorry, the patch applied against my tree where I use this hack for
"slow" device. I will rebase the patch against bluetooth-next.

Best regards 
Andrei Emeltchenko 


  reply	other threads:[~2012-06-14 14:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-14  7:45 [PATCH] Bluetooth: Use AUTO_OFF constant in jiffies Andrei Emeltchenko
2012-06-14 12:07 ` Anderson Lizardo
2012-06-14 14:22   ` Andrei Emeltchenko [this message]
2012-06-15  7:36   ` [PATCHv2] " Andrei Emeltchenko
2012-06-19  3:11     ` Gustavo Padovan

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=20120614142214.GA2585@aemeltch-MOBL1 \
    --to=andrei.emeltchenko.news@gmail.com \
    --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