From: "Gix, Brian" <brian.gix@intel.com>
To: "michal.lowas-rzechonek@silvair.com"
<michal.lowas-rzechonek@silvair.com>,
"linux-bluetooth@vger.kernel.org"
<linux-bluetooth@vger.kernel.org>
Subject: Re: [PATCH BlueZ v3 0/1] mesh: Use node uuids as storage directory names
Date: Wed, 8 May 2019 19:13:53 +0000 [thread overview]
Message-ID: <1557342831.14401.0.camel@intel.com> (raw)
In-Reply-To: <20190508142445.4508-1-michal.lowas-rzechonek@silvair.com>
Patch Applied
On Wed, 2019-05-08 at 16:24 +0200, Michał Lowas-Rzechonek wrote:
> This version of the patch drops direct asprintf() calls in favor of
> l_strdup_printf.
>
> Michał Lowas-Rzechonek (1):
> mesh: Use node uuids as storage directory names
>
> doc/mesh-api.txt | 26 ++++++++++---
> mesh/README | 7 ++--
> mesh/mesh-db.c | 4 --
> mesh/mesh-db.h | 1 -
> mesh/mesh.c | 7 ++++
> mesh/node.c | 38 ++++++-------------
> mesh/node.h | 2 +-
> mesh/storage.c | 96 +++++++++++++++---------------------------------
> 8 files changed, 72 insertions(+), 109 deletions(-)
>
prev parent reply other threads:[~2019-05-08 19:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-08 14:24 [PATCH BlueZ v3 0/1] mesh: Use node uuids as storage directory names Michał Lowas-Rzechonek
2019-05-08 14:24 ` [PATCH BlueZ v3 1/1] " Michał Lowas-Rzechonek
2019-05-08 19:13 ` 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=1557342831.14401.0.camel@intel.com \
--to=brian.gix@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).