From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: barebox@lists.infradead.org
Subject: [PATCH v2 0/3] state: add support for pre-mainline state format
Date: Thu, 28 Sep 2017 11:03:26 +0200 [thread overview]
Message-ID: <20170928090329.28006-1-u.kleine-koenig@pengutronix.de> (raw)
Hello,
when the state framework was developed the underlying raw format was
simpler (only one checksum and no length) and no meta data for direct
buckets.
To be able to keep the binary representation with the current state
framework this patch series introduces the old "raw" format as
"rawcompat" and teaches the direct bucket backend to skip writing meta
data in some cases.
This is v2 of the series, compared to v1 this also updates the
documentation.
Best regards
Uwe
Uwe Kleine-König (3):
Documentation: state: adapt description to reality
state: new backend format "rawcompat"
state: storage: direct: skip writing meta data if this makes data fit
.../devicetree/bindings/barebox/barebox,state.rst | 25 ++--
common/state/Makefile | 1 +
common/state/backend_bucket_direct.c | 23 +++-
common/state/backend_format_rawcompat.c | 145 +++++++++++++++++++++
common/state/state.c | 3 +
common/state/state.h | 2 +
6 files changed, 183 insertions(+), 16 deletions(-)
create mode 100644 common/state/backend_format_rawcompat.c
--
2.11.0
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next reply other threads:[~2017-09-28 9:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-28 9:03 Uwe Kleine-König [this message]
2017-09-28 9:03 ` [PATCH v2 1/3] Documentation: state: adapt description to reality Uwe Kleine-König
2017-09-28 10:53 ` Sascha Hauer
2017-09-28 9:03 ` [PATCH v2 2/3] state: new backend format "rawcompat" Uwe Kleine-König
2017-09-28 9:03 ` [PATCH v2 3/3] state: storage: direct: skip writing meta data if this makes data fit Uwe Kleine-König
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=20170928090329.28006-1-u.kleine-koenig@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--cc=barebox@lists.infradead.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