linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Justin TerAvest <teravest@google.com>
Cc: Bluez mailing list <linux-bluetooth@vger.kernel.org>,
	jpawlowski@google.com, Johan Hedberg <johan.hedberg@intel.com>
Subject: Re: [PATCH] Bluetooth: btusb: Add quirk for BTUSB_INTEL_NEW
Date: Thu, 27 Sep 2018 12:29:02 +0200	[thread overview]
Message-ID: <8674BF84-BE2E-466F-8A9C-2D9DC3F86F67@holtmann.org> (raw)
In-Reply-To: <20180925170457.33979-1-teravest@google.com>

Hi Justin,

> Intel "new" controllers can do both LE scan and BR/EDR inquiry at once.
> 
> Signed-off-by: Justin TerAvest <teravest@google.com>
> ---
> drivers/bluetooth/btusb.c | 1 +
> 1 file changed, 1 insertion(+)

patch has been applied to bluetooth-next tree.

Regards

Marcel


      reply	other threads:[~2018-09-27 10:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-25 17:04 [PATCH] Bluetooth: btusb: Add quirk for BTUSB_INTEL_NEW Justin TerAvest
2018-09-27 10:29 ` Marcel Holtmann [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=8674BF84-BE2E-466F-8A9C-2D9DC3F86F67@holtmann.org \
    --to=marcel@holtmann.org \
    --cc=johan.hedberg@intel.com \
    --cc=jpawlowski@google.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=teravest@google.com \
    /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).