linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "John W. Linville" <linville@tuxdriver.com>
To: Gustavo Padovan <gustavo@padovan.org>,
	linux-wireless@vger.kernel.org, linux-bluetooth@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: pull request: bluetooth-next 2014-06-01
Date: Thu, 5 Jun 2014 14:10:18 -0400	[thread overview]
Message-ID: <20140605181018.GE3621@tuxdriver.com> (raw)
In-Reply-To: <20140602140636.GA1659@joana>

On Mon, Jun 02, 2014 at 11:06:36AM -0300, Gustavo Padovan wrote:
> Hi John,
> 
> Here some more patches for 3.16. We know that Linus already opened the merge
> window, but this is fix only pull request, and most of the patches here are
> also tagged for stable.
> 
> Please pull! or let me know of any issues. Thanks!
> 
> 	Gustavo
> 
> ---
> The following changes since commit d7b2545023ecfde94d3ea9c03c5480ac18da96c9:
> 
>   Bluetooth: Clearly distinguish mgmt LTK type from authenticated property (2014-05-23 11:24:04 -0700)
> 
> are available in the git repository at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-next.git for-upstream
> 
> for you to fetch changes up to 8a96f3cd22878fc0bb564a8478a6e17c0b8dca73:
> 
>   Bluetooth: Fix L2CAP deadlock (2014-06-02 13:38:19 +0300)

Pulling now...

-- 
John W. Linville		Someday the world will need a hero, and you
linville@tuxdriver.com			might be all we have.  Be ready.

      reply	other threads:[~2014-06-05 18:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-02 14:06 pull request: bluetooth-next 2014-06-01 Gustavo Padovan
2014-06-05 18:10 ` 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=20140605181018.GE3621@tuxdriver.com \
    --to=linville@tuxdriver.com \
    --cc=gustavo@padovan.org \
    --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).