public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Zhihao Cheng <chengzhihao1@huawei.com>
To: Rickard Andersson <rickard.andersson@axis.com>, <richard@nod.at>,
	<linux-mtd@lists.infradead.org>, <rickard314.andersson@gmail.com>
Cc: <kernel@axis.com>
Subject: Re: [PATCH v2 08/10] ubi: Add max erase counter sysfs attribute for fastmap area
Date: Fri, 11 Oct 2024 20:06:32 +0800	[thread overview]
Message-ID: <9a7f1df8-2695-9eee-cc01-7cb36cc0fdeb@huawei.com> (raw)
In-Reply-To: <20241011092134.2909496-8-rickard.andersson@axis.com>

在 2024/10/11 17:21, Rickard Andersson 写道:
> A max erase counter specifically for the fastmap area gives a better
> understanding of the flash wear.
> 
> Signed-off-by: Rickard Andersson <rickard.andersson@axis.com>
> ---
>   Documentation/ABI/stable/sysfs-class-ubi | 8 ++++++++
>   1 file changed, 8 insertions(+)

Reviewed-by: Zhihao Cheng <chengzhihao1@huawei.com>
> 
> diff --git a/Documentation/ABI/stable/sysfs-class-ubi b/Documentation/ABI/stable/sysfs-class-ubi
> index 05a701b03a9a..62c93fda0bc4 100644
> --- a/Documentation/ABI/stable/sysfs-class-ubi
> +++ b/Documentation/ABI/stable/sysfs-class-ubi
> @@ -78,6 +78,14 @@ Contact:	Artem Bityutskiy <dedekind@infradead.org>
>   Description:
>   		Maximum physical eraseblock erase counter value.
>   
> +What:		/sys/class/ubi/ubiX/max_ec_fastmap
> +Date:		October 2024
> +KernelVersion:	6.X
> +Contact:	linux-mtd@lists.infradead.org
> +Description:
> +		Maximum physical eraseblock erase counter value for a block
> +		in the fastmap area.
> +
>   What:		/sys/class/ubi/ubiX/max_vol_count
>   Date:		July 2006
>   KernelVersion:	2.6.22
> 


______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/

  reply	other threads:[~2024-10-11 12:17 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-11  9:21 [PATCH v2 01/10] ubi: Expose mean erase counter in sysfs Rickard Andersson
2024-10-11  9:21 ` [PATCH v2 02/10] ubi: Expose mean erase counter for fastmap " Rickard Andersson
2024-10-11 12:02   ` Zhihao Cheng
2024-10-11  9:21 ` [PATCH v2 03/10] ubi: Expose max " Rickard Andersson
2024-10-11 12:03   ` Zhihao Cheng
2024-10-11  9:21 ` [PATCH v2 04/10] ubi: Expose mean erase counter for data " Rickard Andersson
2024-10-11 12:04   ` Zhihao Cheng
2024-10-11  9:21 ` [PATCH v2 05/10] ubi: Expose max " Rickard Andersson
2024-10-11 12:04   ` Zhihao Cheng
2024-10-11  9:21 ` [PATCH v2 06/10] ubi: Add mean erase counter sysfs attribute Rickard Andersson
2024-10-11 12:06   ` Zhihao Cheng
2024-10-11  9:21 ` [PATCH v2 07/10] ubi: Add mean erase counter sysfs attribute for fastmap area Rickard Andersson
2024-10-11 12:06   ` Zhihao Cheng
2024-10-11  9:21 ` [PATCH v2 08/10] ubi: Add max " Rickard Andersson
2024-10-11 12:06   ` Zhihao Cheng [this message]
2024-10-11  9:21 ` [PATCH v2 09/10] ubi: Add mean erase counter sysfs attribute for data area Rickard Andersson
2024-10-11 12:08   ` Zhihao Cheng
2024-10-11  9:21 ` [PATCH v2 10/10] ubi: Add max " Rickard Andersson
2024-10-11 12:08   ` Zhihao Cheng
2024-10-11 12:01 ` [PATCH v2 01/10] ubi: Expose mean erase counter in sysfs Zhihao Cheng

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=9a7f1df8-2695-9eee-cc01-7cb36cc0fdeb@huawei.com \
    --to=chengzhihao1@huawei.com \
    --cc=kernel@axis.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=richard@nod.at \
    --cc=rickard.andersson@axis.com \
    --cc=rickard314.andersson@gmail.com \
    /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