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

Message-ID: <20130422185713.GE2055@tuxdriver.com>
Date:	Mon, 22 Apr 2013 14:57:14 -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 2013-04-18

On Thu, Apr 18, 2013 at 01:48:36AM -0300, Gustavo Padovan wrote:
> Hi John,
> 
> A set of changes intended for 3.10. The biggest changes here are from David
> Herrmann, he rewrote most of the HIDP layer making it more reliable. Marcel
> added a driver setup stage for device that need special handling on their
> early initialization. Other than that we have the usual clean ups, bugfixes
> and small improvements.
> 
> Please pull or let me know of any problems! Thanks!
> 
> 	Gustavo
> 
> ---
> The following changes since commit 84bcc0c3c4b8ca4c0abed2d2dd63b7ce04f8be0e:
> 
>   brcmfmac: enable sk_buff queueing when credits deplete (2013-04-03 15:07:09 -0400)
> 
> 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 76a388beaf92cc75b829d4a0b7d69afaaeaa4b0a:
> 
>   Bluetooth: Rename LE_SCANNING_* macros (2013-04-18 01:17:27 -0300)

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/