From: "michal.lowas-rzechonek@silvair.com" <michal.lowas-rzechonek@silvair.com>
To: "Gix, Brian" <brian.gix@intel.com>
Cc: "linux-bluetooth@vger.kernel.org"
<linux-bluetooth@vger.kernel.org>,
"Stotland, Inga" <inga.stotland@intel.com>
Subject: Re: [PATCH BlueZ 2/3] mesh: Add DevKeySend call
Date: Fri, 28 Jun 2019 19:18:44 +0200 [thread overview]
Message-ID: <20190628171844.3jy7lvwewff2i7c6@kynes> (raw)
In-Reply-To: <1561732393.7802.50.camel@intel.com>
Brian,
On 06/28, Gix, Brian wrote:
> > I have a question here: what's the idea behind net_index argument in
> > this API? There is no such argument in regular Send() call, and I don't
>
> Unlike App Keys, Device keys do not have a bound Net Key...
Right. Thanks for the explanation (and patience...). I'll send v2 after
the weekend.
regards
--
Michał Lowas-Rzechonek <michal.lowas-rzechonek@silvair.com>
Silvair http://silvair.com
Jasnogórska 44, 31-358 Krakow, POLAND
next prev parent reply other threads:[~2019-06-28 17:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-28 12:52 [PATCH BlueZ 0/3] Add support for remote dev keys Michał Lowas-Rzechonek
2019-06-28 12:52 ` [PATCH BlueZ 1/3] mesh: Rename APP_IDX_DEV to APP_IDX_DEV_LOCAL, add APP_IDX_DEV_REMOTE Michał Lowas-Rzechonek
2019-06-28 12:52 ` [PATCH BlueZ 2/3] mesh: Add DevKeySend call Michał Lowas-Rzechonek
2019-06-28 13:29 ` Michał Lowas-Rzechonek
2019-06-28 14:33 ` Gix, Brian
2019-06-28 17:18 ` michal.lowas-rzechonek [this message]
2019-07-01 20:00 ` michal.lowas-rzechonek
2019-07-01 20:08 ` Gix, Brian
2019-07-01 20:14 ` michal.lowas-rzechonek
2019-06-28 12:52 ` [PATCH BlueZ 3/3] mesh: Handle messages encrypted with a remote dev key Michał Lowas-Rzechonek
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=20190628171844.3jy7lvwewff2i7c6@kynes \
--to=michal.lowas-rzechonek@silvair.com \
--cc=brian.gix@intel.com \
--cc=inga.stotland@intel.com \
--cc=linux-bluetooth@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