From: "Michał Lowas-Rzechonek" <michal.lowas-rzechonek@silvair.com>
To: linux-bluetooth@vger.kernel.org
Cc: brian.gix@intel.com, inga.stotland@intel.com
Subject: Re: [PATCH RESEND BlueZ v3 0/1] mesh: Streamline crypto functions
Date: Thu, 16 Jan 2020 19:22:06 +0100 [thread overview]
Message-ID: <20200116182206.eo6un6kegdsckwai@kynes> (raw)
In-Reply-To: <20200113123110.2209-1-michal.lowas-rzechonek@silvair.com>
Hi Brian,
On 01/13, Michał Lowas-Rzechonek wrote:
> This is a followup to commits 79fd24af1 45beec16b and 37bbe30c9,
> continuing a cleanup of mesh/crypto.
>
> This version works with unit tests added in 06cf0fd1c.
Any chances to apply this, or is there something I should improve?
--
Michał Lowas-Rzechonek <michal.lowas-rzechonek@silvair.com>
Silvair http://silvair.com
Jasnogórska 44, 31-358 Krakow, POLAND
prev parent reply other threads:[~2020-01-16 18:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-13 12:31 [PATCH RESEND BlueZ v3 0/1] mesh: Streamline crypto functions Michał Lowas-Rzechonek
2020-01-13 12:31 ` [PATCH BlueZ v3 1/1] mesh: Refactor mesh/crypto Michał Lowas-Rzechonek
2020-01-16 18:22 ` Michał Lowas-Rzechonek [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=20200116182206.eo6un6kegdsckwai@kynes \
--to=michal.lowas-rzechonek@silvair.com \
--cc=brian.gix@intel.com \
--cc=inga.stotland@intel.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;
as well as URLs for NNTP newsgroup(s).