From: "michal.lowas-rzechonek@silvair.com" <michal.lowas-rzechonek@silvair.com>
To: "Stotland, Inga" <inga.stotland@intel.com>
Cc: "linux-bluetooth@vger.kernel.org"
<linux-bluetooth@vger.kernel.org>,
"Gix, Brian" <brian.gix@intel.com>
Subject: Re: [PATCH BlueZ] mesh: Clean up includes
Date: Wed, 19 Jun 2019 19:44:03 +0200 [thread overview]
Message-ID: <20190619174403.yhrey4dkxges2ggi@kynes> (raw)
In-Reply-To: <6b160fc3a67b72495bd533a884ae7edd2d39c47b.camel@intel.com>
Hi Inga,
On 06/18, Stotland, Inga wrote:
> I don't disagree, this was sort of an "intermediate" patch. I'd prefer
> to remove the reference to json from storage.c and the rest of the code
> and localize it in only one file that would deal with json-related
> processing.
>
> So I might just as well go ahead and make mesh-db.h a generic API to
> allow for different storage formats (even though for now we have only
> json defined format).
Sounds good! If that's the goal, please go ahead with the patch and any
further ones. I'm very much interested in using non-JSON storage, as
more granular format might be better suited for embedded devices (flash
wear, power failures and whatnot).
FYI, you've probably noticed I'm attempting a similar thing with mesh-io
layer.
best regards
--
Michał Lowas-Rzechonek <michal.lowas-rzechonek@silvair.com>
Silvair http://silvair.com
Jasnogórska 44, 31-358 Krakow, POLAND
prev parent reply other threads:[~2019-06-19 17:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-17 21:38 [PATCH BlueZ] mesh: Clean up includes Inga Stotland
2019-06-18 7:35 ` Michał Lowas-Rzechonek
2019-06-18 15:49 ` Stotland, Inga
2019-06-19 17:44 ` michal.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=20190619174403.yhrey4dkxges2ggi@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