U-Boot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Vasileios Amoiridis <vassilisamir@gmail.com>
To: trini@konsulko.com, hs@denx.de, pro@denx.de
Cc: vasileios.amoiridis@cern.ch, u-boot@lists.denx.de
Subject: [RFC PATCH 0/1] drivers: bootcount: Add support for FAT filesystem
Date: Wed,  5 Jun 2024 20:10:40 +0200	[thread overview]
Message-ID: <20240605181041.68317-1-vassilisamir@gmail.com> (raw)

From: Vasileios Amoiridis <vasileios.amoiridis@cern.ch>

This patch adds support to save the bootcount variable in a file located in
FAT filesystem. Up to now, there was support only for EXT filesystem.

The reason I put this as RFC is because the file "bootcount_ext.c" will no
longer represent the implementation for the EXT filesystem, but also for the
FAT filesystem. Should it be renamed? If not, wouldn't it be inconsistent?

Cheers,
Vasilis

P.S: Documentation has not been modified yet, I will submit in the v2 (if any).

Vasileios Amoiridis (1):
  drivers: bootcount: Add support for FAT filesystem

 doc/README.bootcount              | 12 ++++----
 drivers/bootcount/Kconfig         | 49 +++++++++++++++++++++++--------
 drivers/bootcount/Makefile        |  2 +-
 drivers/bootcount/bootcount_ext.c | 18 ++++++++----
 4 files changed, 56 insertions(+), 25 deletions(-)


base-commit: c0ea27bccfb7d2d37fd36806ac2a2f7389099420
-- 
2.34.1


             reply	other threads:[~2024-06-05 19:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-05 18:10 Vasileios Amoiridis [this message]
2024-06-05 18:10 ` [RFC PATCH] drivers: bootcount: Add support for FAT filesystem Vasileios Amoiridis
2024-06-06  7:58   ` Philip Oberfichtner
2024-06-06 17:11     ` Vasileios Amoiridis
2024-06-06 15:34   ` Quentin Schulz
2024-06-06 17:33     ` Vasileios Amoiridis
2024-06-05 18:48 ` [RFC PATCH 0/1] " Tom Rini

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=20240605181041.68317-1-vassilisamir@gmail.com \
    --to=vassilisamir@gmail.com \
    --cc=hs@denx.de \
    --cc=pro@denx.de \
    --cc=trini@konsulko.com \
    --cc=u-boot@lists.denx.de \
    --cc=vasileios.amoiridis@cern.ch \
    /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