linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "K, SpoorthiX" <spoorthix.k@intel.com>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: "linux-bluetooth@vger.kernel.org"
	<linux-bluetooth@vger.kernel.org>,
	"Panda, Bharat B" <bharat.b.panda@intel.com>
Subject: RE: [PATCH] v3 Fast Advertising Interval
Date: Tue, 16 Jul 2019 03:43:46 +0000	[thread overview]
Message-ID: <6AFF54953E047B42BC60A96154D42C5CD472A6@BGSMSX101.gar.corp.intel.com> (raw)
In-Reply-To: <FBF9BD43-EE1B-4D20-853C-19301B5573A0@holtmann.org>

Hi Marcel,

	Thank you for applying the patch.

Regards,
Spoorthi

-----Original Message-----
From: Marcel Holtmann [mailto:marcel@holtmann.org] 
Sent: Monday, July 15, 2019 10:44 PM
To: K, SpoorthiX <spoorthix.k@intel.com>
Cc: linux-bluetooth@vger.kernel.org; Panda, Bharat B <bharat.b.panda@intel.com>
Subject: Re: [PATCH] v3 Fast Advertising Interval

Hi Spoorthi,

> Changes made to add support for fast advertising interval as per core 
> 4.1 specification, section 9.3.11.2.
> 
> A peripheral device entering any of the following GAP modes and 
> sending either non-connectable advertising events or scannable 
> undirected advertising events should use adv_fast_interval2 (100ms - 
> 150ms) for adv_fast_period(30s).
> 
>         - Non-Discoverable Mode
>         - Non-Connectable Mode
>         - Limited Discoverable Mode
>         - General Discoverable Mode
> 
> Signed-off-by: Spoorthi Ravishankar Koppad <spoorthix.k@intel.com>
> ---
> include/net/bluetooth/hci_core.h |  2 ++
> net/bluetooth/hci_request.c      | 32 ++++++++++++++++++++++----------
> 2 files changed, 24 insertions(+), 10 deletions(-)

patch has been applied to bluetooth-next tree.

Regards

Marcel


      reply	other threads:[~2019-07-16  3:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-15 11:35 [PATCH] v3 Fast Advertising Interval spoorthix.k
2019-07-15 17:14 ` Marcel Holtmann
2019-07-16  3:43   ` K, SpoorthiX [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=6AFF54953E047B42BC60A96154D42C5CD472A6@BGSMSX101.gar.corp.intel.com \
    --to=spoorthix.k@intel.com \
    --cc=bharat.b.panda@intel.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=marcel@holtmann.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).