All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johan Hedberg <johan.hedberg@gmail.com>
To: "Arun K. Singh" <arunkat@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH 2/2] Bluetooth: Automate remote name requests
Date: Mon, 22 Nov 2010 08:12:43 +0100	[thread overview]
Message-ID: <20101122071243.GA23443@jh-x301> (raw)
In-Reply-To: <AANLkTinMq-3K09y-bCWM1Z254FsWoRuZ=QEuZM11WPMb@mail.gmail.com>

Hi Arun,

On Mon, Nov 22, 2010, Arun K. Singh wrote:
> > The code will work sub-optimally with userspace versions that still
> > do the name requesting themselves (it shouldn't break anything
> > though) so it is recommended to combine this with a userspace
> > software version that doesn't have automated name requests.
> 
> Could you be bit more explicit about such user space versions that you
> recommend? Would latest bluez versions such as 4.80 qualify for your
> recommendation?

The automated name requests upon "connect complete" events were removed
in 4.78 so any version from there onwards would qualify.

Johan

  parent reply	other threads:[~2010-11-22  7:12 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-18 20:22 [PATCH 1/2] Bluetooth: Create a unified authentication request function johan.hedberg
2010-11-18 20:22 ` [PATCH 2/2] Bluetooth: Automate remote name requests johan.hedberg
2010-11-18 21:31   ` Gustavo F. Padovan
     [not found]   ` <AANLkTinMq-3K09y-bCWM1Z254FsWoRuZ=QEuZM11WPMb@mail.gmail.com>
2010-11-22  5:04     ` Arun K. Singh
2010-11-22  7:12     ` Johan Hedberg [this message]
2010-11-22 20:35       ` Luiz Augusto von Dentz
2010-11-22 21:51         ` Johan Hedberg
  -- strict thread matches above, loose matches on Subject: below --
2010-11-17 22:31 [PATCH 1/2] Bluetooth: Create a unified authentication request function johan.hedberg
2010-11-17 22:31 ` [PATCH 2/2] Bluetooth: Automate remote name requests johan.hedberg

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=20101122071243.GA23443@jh-x301 \
    --to=johan.hedberg@gmail.com \
    --cc=arunkat@gmail.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.