All of 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, quentin.schulz@cherry.de,
	u-boot@lists.denx.de,
	Vasileios Amoiridis <vassilisamir@gmail.com>
Subject: [PATCH v2 0/1]: drivers: bootcount: Add support for FAT filesystem
Date: Mon, 10 Jun 2024 20:51:15 +0200	[thread overview]
Message-ID: <20240610185116.353604-1-vassilisamir@gmail.com> (raw)

Changes in v2:
	- Use generic code by utilizing FS_TYPE_ANY
	- Change filename from bootcount_ext.c to bootcount_fs.c

v1: https://lore.kernel.org/u-boot/20240605181041.68317-1-vassilisamir@gmail.com/

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                     | 53 +++++++++++++------
 drivers/bootcount/Makefile                    |  2 +-
 .../{bootcount_ext.c => bootcount_fs.c}       | 12 ++---
 4 files changed, 50 insertions(+), 29 deletions(-)
 rename drivers/bootcount/{bootcount_ext.c => bootcount_fs.c} (81%)

-- 
2.25.1


             reply	other threads:[~2024-06-10 18:54 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-10 18:51 Vasileios Amoiridis [this message]
2024-06-10 18:51 ` [PATCH v2 1/1] drivers: bootcount: Add support for FAT filesystem Vasileios Amoiridis
2024-06-10 19:37   ` Tom Rini
2024-06-10 20:03     ` Vasileios Amoiridis
2024-06-10 20:04       ` Tom Rini
2024-06-11  4:03   ` Heiko Schocher
2024-06-11  9:33   ` Quentin Schulz
2024-06-11 15:27     ` Vasileios Amoiridis
2024-06-11 15:41       ` Quentin Schulz
2024-06-11 16:06         ` Tom Rini
2024-06-11 16:20           ` Vasileios Amoiridis
2024-06-11 16:29             ` Quentin Schulz
2024-06-11 20:30               ` Vasileios Amoiridis
2024-06-11 16:16         ` Vasileios Amoiridis

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=20240610185116.353604-1-vassilisamir@gmail.com \
    --to=vassilisamir@gmail.com \
    --cc=hs@denx.de \
    --cc=pro@denx.de \
    --cc=quentin.schulz@cherry.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.