Received-SPF: pass (google.com: domain of linux-bluetooth-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
IronPort-SDR: aZ7H6hwem02XFzVgKctKqNLLFpeYF+O5c+ZsJef9V0lS2JDQTKWlB+AkRNNx71GmtGE+AE7UYN
 o8Oisaw9uyUQ==
IronPort-SDR: ryAPiiQfNPUtxoPwoMsp+hr7NhpQZdUHyxAa8OiXWp46uI6Wap9qWXa4J1r6p3aIgLFUDDYGr8
 2i2eQKbrYjMw==
From:   Inga Stotland <inga.stotland@intel.com>
To:     linux-bluetooth@vger.kernel.org
Cc:     brian.gix@intel.com, michal.lowas-rzechonek@silvair.com,
        Inga Stotland <inga.stotland@intel.com>
Subject: [PATCH BlueZ v2 0/4] Use compliant UUID for mesh
Date:   Fri, 12 Feb 2021 13:42:40 -0800
Message-Id: <20210212214244.74995-1-inga.stotland@intel.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Precedence: bulk

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(-)

-- 
2.26.2