Return-path: Received: from charlotte.tuxdriver.com ([70.61.120.58]:34803 "EHLO smtp.tuxdriver.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751428AbaHOPAI (ORCPT ); Fri, 15 Aug 2014 11:00:08 -0400 Date: Fri, 15 Aug 2014 10:45:45 -0400 From: "John W. Linville" To: linux-wireless@vger.kernel.org, linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: pull request: bluetooth-next 2014-08-14 Message-ID: <20140815144545.GL4953@tuxdriver.com> (sfid-20140815_170047_672934_89773FBB) References: <20140814145000.GA14226@t440s.P-661HNU-F1> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: <20140814145000.GA14226@t440s.P-661HNU-F1> Sender: linux-wireless-owner@vger.kernel.org List-ID: On Thu, Aug 14, 2014 at 05:50:00PM +0300, Johan Hedberg wrote: > Hi John, > > Here's our first bluetooth-next pull request for the 3.18 kernel. Our > tree is based on net-next so you'd need to pull from there first before > pulling from our tree. What did you need from net-next that made you base on that instead of wireless-next? I generally like to decide for myself what level of net-next needs to be the base of wireless-next... John -- John W. Linville Someday the world will need a hero, and you linville@tuxdriver.com might be all we have. Be ready.