linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: johan.hedberg@gmail.com
Cc: netdev@vger.kernel.org, linux-bluetooth@vger.kernel.org
Subject: Re: pull request: bluetooth-next 2019-02-24
Date: Sun, 24 Feb 2019 22:27:47 -0800 (PST)	[thread overview]
Message-ID: <20190224.222747.1583677905953396590.davem@davemloft.net> (raw)
In-Reply-To: <20190224083634.GA82295@jhedberg-mac01.home>

From: Johan Hedberg <johan.hedberg@gmail.com>
Date: Sun, 24 Feb 2019 10:36:34 +0200

> Here's the main bluetooth-next pull request for the 5.1 kernel.
> 
>  - Fixes & improvements to mediatek, hci_qca, btrtl, and btmrvl HCI drivers
>  - Fixes to parsing invalid L2CAP config option sizes
>  - Locking fix to bt_accept_enqueue()
>  - Add support for new Marvel sd8977 chipset
>  - Various other smaller fixes & cleanups
> 
> Please let me know if there are any issues pulling. Thanks.

Pulled, thanks Johan.

      reply	other threads:[~2019-02-25  6:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-24  8:36 pull request: bluetooth-next 2019-02-24 Johan Hedberg
2019-02-25  6:27 ` 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=20190224.222747.1583677905953396590.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=johan.hedberg@gmail.com \
    --cc=linux-bluetooth@vger.kernel.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).