linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sathish Narasimman <nsathish41@gmail.com>
To: Bluez mailing list <linux-bluetooth@vger.kernel.org>,
	Chethan T N <chethan.tumkur.narayan@intel.com>,
	Marcel Holtmann <marcel@holtmann.org>
Cc: Sathish Narasimman <sathish.narasimman@intel.com>
Subject: Re: [PATCH v2 0/7] LL Privacy support
Date: Mon, 8 Jun 2020 12:00:14 +0530	[thread overview]
Message-ID: <CAOVXEJLCrZUi0VNJKMBMwhe4-SvhifParsWHXY3TQEuqG_H5Jw@mail.gmail.com> (raw)
In-Reply-To: <20200603171713.9882-1-sathish.narasimman@intel.com>

Hi

On Wed, Jun 3, 2020 at 10:44 PM Sathish Narasimman <nsathish41@gmail.com> wrote:
>
> Based on the input the patches modified and verifed accordingly.
>
> Marcel Holtmann (3):
>   Bluetooth: Translate additional address type correctly
>   Bluetooth: Configure controller address resolution if available
>   Bluetooth: Update resolving list when updating whitelist
>
> Sathish Narasimman (4):
>   Bluetooth: Translate additional address type during le_conn
>   Bluetooth: Let controller creates RPA during le create conn
>   Bluetooth: Enable/Disable address resolution during le create conn
>   Bluetooth: Enable RPA Timeout
>
>  include/net/bluetooth/hci.h      |   8 ++-
>  include/net/bluetooth/hci_core.h |   3 +
>  net/bluetooth/hci_conn.c         |   6 +-
>  net/bluetooth/hci_core.c         |  17 +++++
>  net/bluetooth/hci_event.c        |  20 ++++++
>  net/bluetooth/hci_request.c      | 119 ++++++++++++++++++++++++++-----
>  net/bluetooth/hci_request.h      |   3 +-
>  net/bluetooth/mgmt.c             |   2 +-
>  8 files changed, 157 insertions(+), 21 deletions(-)
>
> --
> 2.17.1
>

Gentle Reminder
Also, the present approach will only work for the central role.

I am planning to work in a peripheral role.
need help with a design approach on the peripheral.


Regards
Sathish N

  parent reply	other threads:[~2020-06-08  6:30 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-03 17:17 [PATCH v2 0/7] LL Privacy support Sathish Narasimman
2020-06-03 17:17 ` [PATCH v2 1/7] Bluetooth: Translate additional address type correctly Sathish Narasimman
2020-06-03 17:17 ` [PATCH v2 2/7] Bluetooth: Configure controller address resolution if available Sathish Narasimman
2020-06-03 17:17 ` [PATCH v2 3/7] Bluetooth: Update resolving list when updating whitelist Sathish Narasimman
2020-06-03 17:17 ` [PATCH 4/7] Bluetooth: Translate additional address type during le_conn Sathish Narasimman
2020-06-03 17:17 ` [PATCH 5/7] Bluetooth: Let controller creates RPA during le create conn Sathish Narasimman
2020-06-03 17:17 ` [PATCH 6/7] Bluetooth: Enable/Disable address resolution " Sathish Narasimman
2020-06-03 17:17 ` [PATCH 7/7] Bluetooth: Enable RPA Timeout Sathish Narasimman
2020-06-08  6:30 ` Sathish Narasimman [this message]
2020-06-19  7:58 ` [PATCH v2 0/7] LL Privacy support Marcel Holtmann
2020-07-01 10:02   ` Sathish Narasimman

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=CAOVXEJLCrZUi0VNJKMBMwhe4-SvhifParsWHXY3TQEuqG_H5Jw@mail.gmail.com \
    --to=nsathish41@gmail.com \
    --cc=chethan.tumkur.narayan@intel.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=marcel@holtmann.org \
    --cc=sathish.narasimman@intel.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).