From: David Miller <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
Date: Tue, 20 Mar 2018 14:25:08 -0400 (EDT) [thread overview]
Message-ID: <20180320.142508.2068698829224047222.davem@davemloft.net> (raw)
In-Reply-To: <D66AC7BA-8BA7-4906-AF69-BBD078CCAF90@holtmann.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.
prev parent reply other threads:[~2018-03-20 18:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-16 18:23 pull request: bluetooth 2018-03-16 Johan Hedberg
2018-03-20 8:44 ` Marcel Holtmann
2018-03-20 14:29 ` David Miller
2018-03-20 17:28 ` Marcel Holtmann
2018-03-20 18:25 ` David Miller [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180320.142508.2068698829224047222.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).