All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Gix, Brian" <brian.gix@intel.com>
To: "linux-bluetooth@vger.kernel.org" <linux-bluetooth@vger.kernel.org>
Cc: "michal.lowas-rzechonek@silvair.com" 
	<michal.lowas-rzechonek@silvair.com>,
	"Stotland, Inga" <inga.stotland@intel.com>
Subject: Re: [PATCH BlueZ 0/3] mesh: add Keyring to CreateNetwork
Date: Wed, 15 May 2019 16:46:25 +0000	[thread overview]
Message-ID: <1557938784.32584.4.camel@intel.com> (raw)
In-Reply-To: <20190514201525.16067-1-brian.gix@intel.com>

Patch-set applied, with minor edit to test-mesh comments

On Tue, 2019-05-14 at 13:15 -0700, Brian Gix wrote:
> Patch-set also fixes some file creation permissions and adds CreateNetwork
> test.
> 
> Brian Gix (3):
>   mesh: Add "create" command to test app
>   mesh: Fix file open error checking and permissions
>   mesh: Save generated Net and Dev keys in KeyRing
> 
>  mesh/keyring.c |  8 +++++---
>  mesh/node.c    | 20 ++++++++++++++++----
>  mesh/storage.c |  2 +-
>  test/test-mesh | 46 ++++++++++++++++++++++++++++++++++++++++++++--
>  4 files changed, 66 insertions(+), 10 deletions(-)
> 

      parent reply	other threads:[~2019-05-15 16:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-14 20:15 [PATCH BlueZ 0/3] mesh: add Keyring to CreateNetwork Brian Gix
2019-05-14 20:15 ` [PATCH BlueZ 1/3] mesh: Add "create" command to test app Brian Gix
2019-05-14 20:15 ` [PATCH BlueZ 2/3] mesh: Fix file open error checking and permissions Brian Gix
2019-05-14 20:15 ` [PATCH BlueZ 3/3] mesh: Save generated Net and Dev keys in KeyRing Brian Gix
2019-05-15 16:46 ` 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=1557938784.32584.4.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.