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, 15 Sep 2014 14:56:59 -0400
From:	"John W. Linville" <linville@...driver.com>
To:	linux-wireless@...r.kernel.org, linux-bluetooth@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: pull request: bluetooth-next 2014-09-14

On Sun, Sep 14, 2014 at 07:24:27AM +0300, Johan Hedberg wrote:
> Hi John,
> 
> On Sun, Sep 14, 2014, Johan Hedberg wrote:
> > Here are some more patches intended for 3.18. Most of them are cleanups
> > or fixes for SMP. The only exception is a fix for BR/EDR L2CAP fixed
> > channels which should now work better together with the L2CAP
> > information request procedure.
> > 
> > Let me know if there are any issues pulling. Thanks.
> > 
> > Johan
> > 
> > ---
> > The following changes since commit 39e90c77637b3892a39f2908aea57539e961c50e:
> > 
> >   Bluetooth: 6lowpan: Route packets that are not meant to peer via correct device (2014-09-09 15:51:47 +0200)
> > 
> > are available in the git repository at:
> > 
> >   git://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-next.git master
> 
> This was supposed to be a reference to the for-upstream branch instead
> of master. Both point to the same commit at this moment but it'd be more
> convenient if you pull from for-upstream so that the master branch can
> continue living on without waiting for the pull to happen. Sorry for the
> extra hassle.
> 
> Johan

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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ