linux-kernel - Re: pull request: bluetooth-next 2012-09-18

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Mon, 24 Sep 2012 19:31:49 -0300
From:	Gustavo Padovan <gustavo@...ovan.org>
To:	"John W. Linville" <linville@...driver.com>
Cc:	"Luis R. Rodriguez" <mcgrof@...not-panic.com>,
	linux-wireless@...r.kernel.org, linux-bluetooth@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: pull request: bluetooth-next 2012-09-18

* John W. Linville <linville@...driver.com> [2012-09-24 15:54:22 -0400]:

> On Mon, Sep 24, 2012 at 03:46:22PM -0300, Gustavo Padovan wrote:
> > * Luis R. Rodriguez <mcgrof@...not-panic.com> [2012-09-21 18:06:42 -0700]:
> > 
> > > On Tue, Sep 18, 2012 at 6:31 PM, Gustavo Padovan <gustavo@...ovan.org> 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:
> 
> <snip>
> 
> > 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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/