Return-Path: Date: Thu, 5 Jun 2014 14:10:18 -0400 From: "John W. Linville" To: Gustavo Padovan , linux-wireless@vger.kernel.org, linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: pull request: bluetooth-next 2014-06-01 Message-ID: <20140605181018.GE3621@tuxdriver.com> References: <20140602140636.GA1659@joana> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: <20140602140636.GA1659@joana> Sender: linux-kernel-owner@vger.kernel.org List-ID: On Mon, Jun 02, 2014 at 11:06:36AM -0300, Gustavo Padovan wrote: > Hi John, > > Here some more patches for 3.16. We know that Linus already opened the merge > window, but this is fix only pull request, and most of the patches here are > also tagged for stable. > > Please pull! or let me know of any issues. Thanks! > > Gustavo > > --- > The following changes since commit d7b2545023ecfde94d3ea9c03c5480ac18da96c9: > > Bluetooth: Clearly distinguish mgmt LTK type from authenticated property (2014-05-23 11:24:04 -0700) > > are available in the git repository at: > > git://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-next.git for-upstream > > for you to fetch changes up to 8a96f3cd22878fc0bb564a8478a6e17c0b8dca73: > > Bluetooth: Fix L2CAP deadlock (2014-06-02 13:38:19 +0300) Pulling now... -- John W. Linville Someday the world will need a hero, and you linville@tuxdriver.com might be all we have. Be ready.