From: "Michał Lowas-Rzechonek" <michal.lowas-rzechonek@silvair.com>
To: Brian Gix <brian.gix@intel.com>
Cc: linux-bluetooth@vger.kernel.org, inga.stotland@intel.com,
jakub.witowski@silvair.com
Subject: Re: [PATCH BlueZ v3 0/1] mesh: Sequence number related fixes
Date: Thu, 16 Jan 2020 19:16:33 +0100 [thread overview]
Message-ID: <20200116181633.rtda4hlxeidzmg54@kynes> (raw)
In-Reply-To: <20200116163908.18041-1-brian.gix@intel.com>
Brian, Jakub,
On 01/16, Brian Gix wrote:
> Adjusted comments for clarity,
Thank you.
> and adjusted the cache-write code to not rewrite the NVM storage if
> nothing has changed, to prevent NVM thrashing if we do reach the
> out-of-range boundary
True.
> I would like both Michal and Jakub's comments on these adjustments.
Thanks again, LGTM.
--
Michał Lowas-Rzechonek <michal.lowas-rzechonek@silvair.com>
Silvair http://silvair.com
Jasnogórska 44, 31-358 Krakow, POLAND
next prev parent reply other threads:[~2020-01-16 18:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-16 16:39 [PATCH BlueZ v3 0/1] mesh: Sequence number related fixes Brian Gix
2020-01-16 16:39 ` [PATCH BlueZ v3 1/1] " Brian Gix
2020-01-16 18:16 ` Michał Lowas-Rzechonek [this message]
2020-01-16 20:51 ` [PATCH BlueZ v3 0/1] " Gix, Brian
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=20200116181633.rtda4hlxeidzmg54@kynes \
--to=michal.lowas-rzechonek@silvair.com \
--cc=brian.gix@intel.com \
--cc=inga.stotland@intel.com \
--cc=jakub.witowski@silvair.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).