Return-path: Received: from mail-yx0-f174.google.com ([209.85.213.174]:59212 "EHLO mail-yx0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751006Ab2IXWb5 (ORCPT ); Mon, 24 Sep 2012 18:31:57 -0400 Date: Mon, 24 Sep 2012 19:31:49 -0300 From: Gustavo Padovan To: "John W. Linville" Cc: "Luis R. Rodriguez" , linux-wireless@vger.kernel.org, linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: pull request: bluetooth-next 2012-09-18 Message-ID: <20120924223149.GB7922@joana> (sfid-20120925_003216_680138_5405F292) References: <20120919013113.GG24689@joana> <20120924184622.GA7922@joana> <20120924195422.GF32351@tuxdriver.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: <20120924195422.GF32351@tuxdriver.com> Sender: linux-wireless-owner@vger.kernel.org List-ID: * John W. Linville [2012-09-24 15:54:22 -0400]: > On Mon, Sep 24, 2012 at 03:46:22PM -0300, Gustavo Padovan wrote: > > * Luis R. Rodriguez [2012-09-21 18:06:42 -0700]: > > > > > On Tue, Sep 18, 2012 at 6:31 PM, Gustavo Padovan wrote: > > > > > > > Johan Hedberg (2): > > > > Bluetooth: mgmt: Implement support for passkey notification > > > > > > Too late now... but why did we allow this a stable fix? I get its a > > > feature that is important and likely overlooked / someone had a brain > > > fart, but from what I gather this is not on v3.5.4 and yet may make it > > > to v3.5.5. At least for backporting this was a bitch: > > > > > Yes, this patch is wrongly marked as stable, it is not even going to 3.5. I'm > > just removing the tag from it and resending the pull request to John. > > Hmmm...well, I already pulled it, and I just pushed it out. Can we live with it? Yes, that would be ok for me. Gustavo