Received-SPF: pass (google.com: best guess record for domain of linux-bluetooth-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
From:   =?UTF-8?q?Micha=C5=82=20Lowas-Rzechonek?= 
        <michal.lowas-rzechonek@silvair.com>
To:     linux-bluetooth@vger.kernel.org
Subject: [PATCH BlueZ v3 0/3] Include destination address in MessageReceived API
Date:   Tue, 26 Nov 2019 15:53:58 +0100
Message-Id: <20191126145401.25129-1-michal.lowas-rzechonek@silvair.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Sender: linux-bluetooth-owner@vger.kernel.org
Precedence: bulk

This patchset changes the MessageReceived API, replacing 'subscription'
flag with destination address of received messages.

The application receives destination address as a D-Bus variant,
containing either as a regular 16bit address (unicast/group) or a
16-octet virtual label.

See previous discussion https://marc.info/?t=156719067300001&r=1&w=2 for
rationale.

v2:
 - fix API in test-join
 - display model subscriptions in test-join and test-mesh

v3:
 - style fixes
 - when adding subscriptions, call UpdateModelConfiguration after subs
   are updated, not before

Michał Lowas-Rzechonek (3):
  mesh: Fix test-join to include mandatory VendorModels property
  mesh: Provide destination address in MessageReceived API
  mesh: Inform application about model subscriptions

 doc/mesh-api.txt |  32 +++++++++++---
 mesh/model.c     | 113 ++++++++++++++++++++++++++++++++++++++++++++---
 test/test-join   |  37 +++++++++++++---
 test/test-mesh   |  33 +++++++-------
 4 files changed, 184 insertions(+), 31 deletions(-)

-- 
2.19.1