Return-path: Received: from charlotte.tuxdriver.com ([70.61.120.58]:51294 "EHLO smtp.tuxdriver.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757831Ab2IXUAX (ORCPT ); Mon, 24 Sep 2012 16:00:23 -0400 Date: Mon, 24 Sep 2012 15:54:22 -0400 From: "John W. Linville" To: Gustavo Padovan , "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: <20120924195422.GF32351@tuxdriver.com> (sfid-20120924_220040_832135_077950F8) References: <20120919013113.GG24689@joana> <20120924184622.GA7922@joana> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: <20120924184622.GA7922@joana> Sender: linux-wireless-owner@vger.kernel.org List-ID: 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? John -- John W. Linville Someday the world will need a hero, and you linville@tuxdriver.com might be all we have. Be ready.