linux-kernel - Re: pull request: bluetooth-next 2014-03-24

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:	Thu, 27 Mar 2014 14:18:49 -0400
From:	"John W. Linville" <linville@...driver.com>
To:	Gustavo Padovan <gustavo@...ovan.org>,
	linux-wireless@...r.kernel.org, linux-bluetooth@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: pull request: bluetooth-next 2014-03-24

On Wed, Mar 26, 2014 at 03:34:11PM -0300, Gustavo Padovan wrote:
> Hi John,
> 
> 2014-03-24 Gustavo Padovan <gustavo@...ovan.org>:
> 
> > Hi John,
> > 
> > Here follow another set of patches to 3.15. This is mostly a bug fix pull
> > request with the exception of one commit from Marcel which adds tracking to
> > the current configured LE scan type parameter.
> 
> There is one more fix that we want to include in this pull request. Here
> follows a new pull request, please pull, Thanks. 
> 
> 	Gustavo
> 
> --
> The following changes since commit 40b552aa5a0bfa785bc7ddb5c2d7965b1e0bb08d:
> 
>   Bluetooth: Enforce strict Secure Connections Only mode security (2014-03-19 23:30:32 +0200)
> 
> 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 e8b1ab9e6d30394e0df3e4f60bf56c4dc9bf0863:
> 
>   Bluetooth: Fix returning peer address in pending connect state (2014-03-26 09:31:33 -0700)

Pulling now...

-- 
John W. Linville		Someday the world will need a hero, and you
linville@...driver.com			might be all we have.  Be ready.
--
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/