mailarchive of the pengutronix oss-tools mailing list
 help / color / mirror / Atom feed
From: Marco Felsch <m.felsch@pengutronix.de>
To: oss-tools@pengutronix.de
Subject: [OSS-Tools] [PATCH dt-utils 0/6] barebox-state sync
Date: Tue, 27 Feb 2024 15:26:05 +0100	[thread overview]
Message-ID: <20240227142611.2421711-1-m.felsch@pengutronix.de> (raw)

Hi,

this re-sync the barebox_state user-space tool with the barebox code.
The reason for the sync is to avoid error prints in case of fresh
initialized barebox state backends.

While on it, I ported a few other commit as well to align the code with
barebox.

Regards,
  Marco

Marco Felsch (6):
  state: align state_backend_bucket_direct_create with barebox
  state: don't mix goto labels and statements on same line
  state: drop null pointer checks around of_delete_node
  treewide: rename struct device_d to device
  state: make uninitialized state less verbose
  state: backend_bucket_direct: add debug prints on read/write

 src/barebox-state.c                         |  4 +++-
 src/barebox-state/backend_bucket_circular.c |  4 ++--
 src/barebox-state/backend_bucket_direct.c   | 25 +++++++++++++++------
 src/barebox-state/backend_format_dtb.c      |  4 ++--
 src/barebox-state/backend_format_raw.c      | 11 +++++----
 src/barebox-state/backend_storage.c         | 24 ++++++++++++--------
 src/barebox-state/state.c                   | 19 +++++++++-------
 src/barebox-state/state.h                   | 24 ++++++++++++--------
 src/barebox-state/state_variables.c         |  9 +++++---
 src/dt/common.h                             | 22 +++++++++---------
 src/dt/dt.h                                 |  8 +++----
 src/libdt.c                                 |  2 +-
 12 files changed, 93 insertions(+), 63 deletions(-)

-- 
2.39.2




             reply	other threads:[~2024-02-27 14:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-27 14:26 Marco Felsch [this message]
2024-02-27 14:26 ` [OSS-Tools] [PATCH dt-utils 1/6] state: align state_backend_bucket_direct_create with barebox Marco Felsch
2024-02-27 14:26 ` [OSS-Tools] [PATCH dt-utils 2/6] state: don't mix goto labels and statements on same line Marco Felsch
2024-02-27 14:26 ` [OSS-Tools] [PATCH dt-utils 3/6] state: drop null pointer checks around of_delete_node Marco Felsch
2024-02-27 14:26 ` [OSS-Tools] [PATCH dt-utils 4/6] treewide: rename struct device_d to device Marco Felsch
2024-02-27 14:26 ` [OSS-Tools] [PATCH dt-utils 5/6] state: make uninitialized state less verbose Marco Felsch
2024-02-27 14:26 ` [OSS-Tools] [PATCH dt-utils 6/6] state: backend_bucket_direct: add debug prints on read/write Marco Felsch

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=20240227142611.2421711-1-m.felsch@pengutronix.de \
    --to=m.felsch@pengutronix.de \
    --cc=oss-tools@pengutronix.de \
    /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