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;
Date:   Sun, 1 Dec 2019 23:13:12 +0100
From:   Aurelien Jarno <aurelien@aurel32.net>
To:     linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH BlueZ] mesh: fix (re)transmit count & interval steps
Message-ID: <20191201221255.GA48051@aurel32.net>
References: <20191111195406.3291-1-aurelien@aurel32.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20191111195406.3291-1-aurelien@aurel32.net>
User-Agent: Mutt/1.12.2 (2019-09-21)
Sender: linux-bluetooth-owner@vger.kernel.org
Precedence: bulk

On 2019-11-11 20:54, Aurelien Jarno wrote:
> The Foundation Model Layer uses little endian ordering. As a
> consequence the (re)transmit count and interval steps in the Config
> Relay, Config Model Publication and Config Network Transmit messages
> use the lower 3 bits for the (re)transmission count and the higher 5
> bits for the interval steps.
> 
> The figure 4.5 in section 4.3.2.16 of the Mesh Profile Bluetooth
> Specification provides a good clarification.
> 
> This patch therefore fixes those messages for both the daemon and
> configuration client parts.

Gentle ping on that patch.

Thanks,
Aurelien

-- 
Aurelien Jarno                          GPG: 4096R/1DDD8C9B
aurelien@aurel32.net                 http://www.aurel32.net