Return-Path: <linux-bluetooth-owner@vger.kernel.org>
Date: Tue, 20 Mar 2018 14:25:08 -0400 (EDT)
Message-Id: <20180320.142508.2068698829224047222.davem@davemloft.net>
To: marcel@holtmann.org
Cc: johan.hedberg@gmail.com, linux-bluetooth@vger.kernel.org,
        netdev@vger.kernel.org
Subject: Re: pull request: bluetooth 2018-03-16
From: David Miller <davem@davemloft.net>
In-Reply-To: <D66AC7BA-8BA7-4906-AF69-BBD078CCAF90@holtmann.org>
References: <2162D348-7B5F-4693-87AB-8835A1638CF3@holtmann.org>
        <20180320.102926.1557866956544440900.davem@davemloft.net>
        <D66AC7BA-8BA7-4906-AF69-BBD078CCAF90@holtmann.org>
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Sender: linux-bluetooth-owner@vger.kernel.org
List-ID: <linux-bluetooth.vger.kernel.org>

From: Marcel Holtmann <marcel@holtmann.org>
Date: Tue, 20 Mar 2018 18:28:18 +0100

> Any chance you can pull net into net-next once you send it off to
> Linus? We have a few further Broadcom driver improvements for
> net-next that conflict a little bit.

Yeah, I merge net into net-next pretty much every time after
Linus pulls from net.

So that will happen.