linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Pali Rohár" <pali.rohar@gmail.com>
To: Johan Hedberg <johan.hedberg@gmail.com>
Cc: Marcel Holtmann <marcel@holtmann.org>,
	Gustavo Padovan <gustavo@padovan.org>,
	linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: 3.19-rc1 refuse connection from bluetooth headset
Date: Wed, 24 Dec 2014 19:41:56 +0100	[thread overview]
Message-ID: <201412241941.56927@pali> (raw)
In-Reply-To: <20141224183737.GA21428@t440s.P-661HNU-DI-F1>

[-- Attachment #1: Type: Text/Plain, Size: 744 bytes --]

On Wednesday 24 December 2014 19:37:37 Johan Hedberg wrote:
> Hi Pali,
> 
> On Wed, Dec 24, 2014, Pali Rohár wrote:
> > > Could you try the attached patch? I think the reason might
> > > be the dependence on the HCI_CONNECTABLE flag that's only
> > > set if the page scan was enabled through mgmt (which
> > > wouldn't be the case with BlueZ 4.98).
> > > 
> > > Johan
> > 
> > Hi Johan! Thanks for quick reply. Your patch fixes my
> > problem and auto-connection of my bluetooth headset is
> > working again. Will you forward patch to mainline kernel?
> 
> Yes, we'll tag it from 3.17.x onwards where this was
> introduced.
> 
> Johan

Ok, you can add my Tested-by line to patch.

-- 
Pali Rohár
pali.rohar@gmail.com

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2014-12-24 18:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-24 17:15 3.19-rc1 refuse connection from bluetooth headset Pali Rohár
2014-12-24 17:36 ` Johan Hedberg
2014-12-24 18:32   ` Pali Rohár
2014-12-24 18:37     ` Johan Hedberg
2014-12-24 18:41       ` Pali Rohár [this message]
2015-02-12 11:22         ` Ethan
2015-02-12 11:34           ` 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=201412241941.56927@pali \
    --to=pali.rohar@gmail.com \
    --cc=gustavo@padovan.org \
    --cc=johan.hedberg@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcel@holtmann.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).