From: <Waldemar.Rymarkiewicz@tieto.com>
To: <keithp@keithp.com>, <padovan@profusion.mobi>
CC: <marcel@holtmann.org>, <linux-bluetooth@vger.kernel.org>,
        <linux-kernel@vger.kernel.org>
Date: Thu, 9 Jun 2011 10:59:32 +0300
Subject: RE: Regression caused by "Bluetooth: Map sec_level to link key
 requirements"
Thread-Topic: Regression caused by "Bluetooth: Map sec_level to link key
 requirements"
Thread-Index: AcwmdcuZTkZgwxL5TPOpu86NujjU4gABBq1g
Message-ID: <99B09243E1A5DA4898CDD8B700111448175AA2DB2A@EXMB04.eu.tieto.com>
References: <yunboy7a2so.fsf@aiko.keithp.com>
In-Reply-To: <yunboy7a2so.fsf@aiko.keithp.com>
Accept-Language: en-US
Content-Language: en-US
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 8BIT
MIME-Version: 1.0
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 871
Lines: 23

Hi Keith, 

>Patch 13d39315c22b128f4796fc008b04914a7c32bb1a is causing a 
>regression From 2.6.39. I cannot communicate with my Nokia 
>N900 using either the SyncML or DUN RFCOMM services.  I get a 
>connection reset error shortly after startup.
>
>I've reverted this patch on top of something past -rc2 (to be 
>precise, I'm branching from ef2398019b305827ea7130ebaf7bf521b444530e).
>With the following fix-up to make things build again, my 
>bluetooth works again.

Logs from kernel and bluez would be much appreciated to see what happend.
As I remember this was pretty well tested with BITE test by Johan.

Thanks,
Waldek

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/