linux-kernel - Re: pull request: bluetooth-next 2013-01-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]

Message-ID: <20130130192147.GC2167@tuxdriver.com>
Date:	Wed, 30 Jan 2013 14:21:47 -0500
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 2013-01-24

On Thu, Jan 24, 2013 at 01:10:52AM -0200, Gustavo Padovan wrote:
> Hi John,
> 
> This is my first pull request to 3.9. The biggest changes here are from Johan
> Hedberg who made a lot of fixes in the Management interface. The issues arose
> due to a new test tool we wrote and the usage of the Management interface as
> default in BlueZ 5. The rest of the patches are more clean ups and small
> fixes.
> 
> Please pull! Thanks!
> 
> 
> 	Gustavo
> ---
> The following changes since commit e7f767a7d9f809c494bfffffeda2bbdbfec110b4:
> 
>   mwifiex: use map/unmap APIs in TX and RX to reduce memcpy (2013-01-07 15:18:30 -0500)
> 
> are available in the git repository at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-next for-upstream
> 
> for you to fetch changes up to 9b008c0457e583e10e62d1215bed6ab26ee54906:
> 
>   Bluetooth: Add support for reading LE supported states (2013-01-23 02:09:16 -0200)

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/