public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: "Gix, Brian" <brian.gix@intel.com>
To: "isak.westin@loytec.com" <isak.westin@loytec.com>,
	"linux-bluetooth@vger.kernel.org"
	<linux-bluetooth@vger.kernel.org>
Subject: Re: [PATCH BlueZ 0/6] Mesh: Fixes for PTS issues
Date: Thu, 6 Oct 2022 21:00:52 +0000	[thread overview]
Message-ID: <28afe97d8dec779a4f1a892442ed61b45777f867.camel@intel.com> (raw)
In-Reply-To: <20221006145927.32731-1-isak.westin@loytec.com>

Hi Isak,

Patches 1-4 of patchset applied.

Patches 5 and 6 have outstanding comments.

Thanks,
--Brian

On Thu, 2022-10-06 at 16:59 +0200, Isak Westin wrote:
> Hi,
> 
> Here is the last patch set with fixes for issues found during PTS
> testing. This covers following tests:
>  - MESH/NODE/PROV/*
>  - MESH/NODE/TNPT/*
>  - MESH/NODE/RLY/*
> 
> Best regards,
> Isak
> 
> Isak Westin (6):
>   mesh: Update Key Refresh flag after provision
>   mesh: provisionee: Handle unknown PDUs
>   mesh: provisionee: Handle failed provisioning
>   mesh: provisionee: Check prov start parameters
>   mesh: Keep canceled SAR data for at least 10 sec
>   mesh: Fix msg cache ring buffer
> 
>  mesh/net.c           | 33 +++++++++++++++++---
>  mesh/node.c          |  4 +--
>  mesh/prov-acceptor.c | 73 +++++++++++++++++++++++++++++++++++-------
> --
>  3 files changed, 90 insertions(+), 20 deletions(-)
> 


  parent reply	other threads:[~2022-10-06 21:01 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-06 14:59 [PATCH BlueZ 0/6] Mesh: Fixes for PTS issues Isak Westin
2022-10-06 14:59 ` [PATCH BlueZ 1/6] mesh: Update Key Refresh flag after provision Isak Westin
2022-10-06 16:22   ` Mesh: Fixes for PTS issues bluez.test.bot
2022-10-06 14:59 ` [PATCH BlueZ 2/6] mesh: provisionee: Handle unknown PDUs Isak Westin
2022-10-06 14:59 ` [PATCH BlueZ 3/6] mesh: provisionee: Handle failed provisioning Isak Westin
2022-10-06 14:59 ` [PATCH BlueZ 4/6] mesh: provisionee: Check prov start parameters Isak Westin
2022-10-06 14:59 ` [PATCH BlueZ 5/6] mesh: Keep canceled SAR data for at least 10 sec Isak Westin
2022-10-06 20:55   ` Gix, Brian
2022-10-07 13:33     ` Isak Westin
2022-10-07 14:56       ` Gix, Brian
2022-10-11 14:13         ` Isak Westin
2022-10-06 14:59 ` [PATCH BlueZ 6/6] mesh: Fix msg cache ring buffer Isak Westin
2022-10-06 20:47   ` Gix, Brian
2022-10-07  8:02     ` Isak Westin
2022-10-07 15:08   ` Gix, Brian
2022-10-06 21:00 ` [PATCH BlueZ 0/6] Mesh: Fixes for PTS issues patchwork-bot+bluetooth
2022-10-06 21:00 ` Gix, Brian [this message]
2022-10-07 15:10 ` patchwork-bot+bluetooth

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=28afe97d8dec779a4f1a892442ed61b45777f867.camel@intel.com \
    --to=brian.gix@intel.com \
    --cc=isak.westin@loytec.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