All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Keith Packard <keithp@keithp.com>
Cc: Johan Hedberg <johan.hedberg@gmail.com>,
	Luiz Augusto von Dentz <luiz.dentz@gmail.com>,
	Waldemar.Rymarkiewicz@tieto.com, padovan@profusion.mobi,
	marcel@holtmann.org, linux-bluetooth@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: Regression caused by "Bluetooth: Map sec_level to link key requirements"
Date: Fri, 24 Jun 2011 22:45:02 -0700	[thread overview]
Message-ID: <4E0575DE.4070004@goop.org> (raw)
In-Reply-To: <yunliwxabmz.fsf@aiko.keithp.com>

On 06/19/2011 12:01 PM, Keith Packard wrote:
>> I think you'll need both of them to fix the pairing/security issues.
> Yup, with both of those patches, I get syncml and dun working again.
>
> (sorry for the delayed testing, I'm traveling)

I just bisected the problems I had reconnecting my Nokia BH-905i
headphones to the same change that Keith identified, and merging
git://git.kernel.org/pub/scm/linux/kernel/git/padovan/bluetooth-2.6.git
into my tree fixed it.

So +1 from me to get this into mainline soon.

Thanks,
    J

  reply	other threads:[~2011-06-25  5:45 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-09  7:20 Regression caused by "Bluetooth: Map sec_level to link key requirements" Keith Packard
2011-06-09  7:59 ` Waldemar.Rymarkiewicz
2011-06-09  7:59   ` Waldemar.Rymarkiewicz
2011-06-09  8:33   ` Johan Hedberg
2011-06-09 17:01     ` Keith Packard
2011-06-09 17:11       ` Waldemar.Rymarkiewicz
2011-06-09 17:11         ` Waldemar.Rymarkiewicz
2011-06-10  5:55         ` Johan Hedberg
2011-06-10  5:58           ` Luiz Augusto von Dentz
2011-06-19 11:11             ` Keith Packard
2011-06-19 17:59               ` Johan Hedberg
2011-06-19 19:01                 ` Keith Packard
2011-06-25  5:45                   ` Jeremy Fitzhardinge [this message]
2011-06-25 19:40                     ` Gustavo F. Padovan
2011-06-09  8:02 ` Waldemar.Rymarkiewicz
2011-06-09  8:02   ` Waldemar.Rymarkiewicz
2011-06-09 17:04   ` Keith Packard

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=4E0575DE.4070004@goop.org \
    --to=jeremy@goop.org \
    --cc=Waldemar.Rymarkiewicz@tieto.com \
    --cc=johan.hedberg@gmail.com \
    --cc=keithp@keithp.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luiz.dentz@gmail.com \
    --cc=marcel@holtmann.org \
    --cc=padovan@profusion.mobi \
    /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.