Return-Path: Content-Type: text/plain; charset=windows-1252 Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1816\)) Subject: Re: l2cap sockets not properly multiplexed on ARM From: Marcel Holtmann In-Reply-To: Date: Thu, 31 Oct 2013 15:19:23 +0100 Cc: Alexander Holler , "linux-bluetooth@vger.kernel.org" Message-Id: References: <5270EC62.6070705@ahsoftware.de>,<5270F19A.4030408@ahsoftware.de> ,<527114A4.5010207@ahsoftware.de> <4A213FF7-48BA-4906-8868-7C3A227EF954@holtmann.org>,<527190DA.6000805@ahsoftware.de>, To: Tim Tisdall Sender: linux-bluetooth-owner@vger.kernel.org List-ID: Hi Tim, > Okay, I got the same issue on an x86 machine running "Linux debian 3.2.0-4-486 #1 Debian 3.2.51-1 i686 GNU/Linux". So, it's not only the ARM machines. > > What versions of the kernel are currently supported by the bluetooth team? (ie when there are bug fixes, how far back will you backport those fixes?) Am I coming across some issue that's already been fixed in newer versions of the kernel? the upstream people are not backporting anything. The closest you get with upstream is if a patch is cheery picked into -stable. For everything else it is the distro?s job to backport. Regards Marcel