From: "Gix, Brian" <brian.gix@intel.com>
To: "linux-bluetooth@vger.kernel.org"
<linux-bluetooth@vger.kernel.org>,
"Stotland, Inga" <inga.stotland@intel.com>
Cc: "michal.lowas-rzechonek@silvair.com"
<michal.lowas-rzechonek@silvair.com>
Subject: Re: [PATCH BlueZ v2 0/4] Use compliant UUID for mesh
Date: Tue, 16 Feb 2021 19:55:04 +0000 [thread overview]
Message-ID: <f56024b1f25c8ee51eb1da2dc66deeea678d92a7.camel@intel.com> (raw)
In-Reply-To: <20210212214244.74995-1-inga.stotland@intel.com>
Patchset Applied
On Fri, 2021-02-12 at 13:42 -0800, Inga Stotland wrote:
> v2: Incorporate Michał's suggestion to use Python's uuid module
> functions.
>
> ************
> Mesh profile spec states that the values use for Device UUIDs
> folow format and generation procedures outlined in RFC 4122.
> This patch set addresses this requirement.
>
>
> Inga Stotland (4):
> doc/mesh-api: Add notion of Device UUID compliance
> mesh: Add validation of Device UUID value
> test/test-mesh: Generate correct value for Device UUID
> tools/mesh-cfg-client:
>
> Makefile.am | 6 ++++--
> doc/mesh-api.txt | 9 ++++++---
> mesh/mesh.c | 18 +++++++++---------
> test/test-mesh | 7 +++----
> tools/mesh-cfgclient.c | 6 +++---
> tools/mesh/mesh-db.c | 2 +-
> 6 files changed, 26 insertions(+), 22 deletions(-)
>
prev parent reply other threads:[~2021-02-16 19:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-12 21:42 [PATCH BlueZ v2 0/4] Use compliant UUID for mesh Inga Stotland
2021-02-12 21:42 ` [PATCH BlueZ v2 1/4] doc/mesh-api: Add notion of Device UUID compliance Inga Stotland
2021-02-12 21:55 ` Use compliant UUID for mesh bluez.test.bot
2021-02-12 21:42 ` [PATCH BlueZ v2 2/4] mesh: Add validation of Device UUID value Inga Stotland
2021-02-12 21:42 ` [PATCH BlueZ v2 3/4] test/test-mesh: Generate correct value for Device UUID Inga Stotland
2021-02-12 21:42 ` [PATCH BlueZ v2 4/4] tools/mesh-cfg-client: Inga Stotland
2021-02-16 19:55 ` Gix, Brian [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=f56024b1f25c8ee51eb1da2dc66deeea678d92a7.camel@intel.com \
--to=brian.gix@intel.com \
--cc=inga.stotland@intel.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=michal.lowas-rzechonek@silvair.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.