From: "John W. Linville" <linville@tuxdriver.com>
To: linux-wireless@vger.kernel.org, linux-bluetooth@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: pull request: bluetooth-next 2014-09-14
Date: Mon, 15 Sep 2014 14:56:59 -0400 [thread overview]
Message-ID: <20140915185659.GD3891@tuxdriver.com> (raw)
In-Reply-To: <20140914042427.GA1926@t440s.P-661HNU-F1>
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@tuxdriver.com might be all we have. Be ready.
prev parent reply other threads:[~2014-09-15 19:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-14 4:19 pull request: bluetooth-next 2014-09-14 Johan Hedberg
2014-09-14 4:24 ` Johan Hedberg
2014-09-15 18:56 ` John W. Linville [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=20140915185659.GD3891@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@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).