From: "Csókás Bence" <csokas.bence@prolan.hu>
To: Miquel Raynal <miquel.raynal@bootlin.com>,
Richard Weinberger <richard@nod.at>
Cc: <linux-mtd@lists.infradead.org>, <linux-kernel@vger.kernel.org>,
"Vignesh Raghavendra" <vigneshr@ti.com>
Subject: Re: [PATCH v3] mtd: Verify written data in paranoid mode
Date: Mon, 12 May 2025 14:29:40 +0200 [thread overview]
Message-ID: <d70952c1-e4ca-4f09-ac23-2ad13e0facc0@prolan.hu> (raw)
In-Reply-To: <87frhambri.fsf@bootlin.com>
Hi,
On 2025. 05. 12. 11:14, Miquel Raynal wrote:
> Why _mtd_verify and not mtd_verify?
Hm, no particular reason, I was thinking that since it's an "internal"
function, like `_mtd_write_oob()`, it would get the underscore. But now
that I think about it, there are many static functions already without
this underscore. Should I change it?
On 2025. 05. 12. 11:45, Richard Weinberger wrote:
> I still have a hard time seeing the benefit of this.
> To me it looks like you're working around broken hardware.
>
> Thanks,
> //richard
Well, yes, in our case. But the point is, we have a strict requirement
for data integrity, which is not unique to us I believe. I would think
there are other industrial control applications like ours, which dictate
a high data integrity.
Bence
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2025-05-12 12:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-12 8:40 [PATCH v3] mtd: Verify written data in paranoid mode Bence Csókás
2025-05-12 9:14 ` Miquel Raynal
2025-05-12 9:45 ` Richard Weinberger
2025-05-12 12:29 ` Csókás Bence [this message]
2025-05-12 12:47 ` Richard Weinberger
2025-05-12 13:13 ` Csókás Bence
2025-05-12 13:59 ` Miquel Raynal
2025-05-12 15:23 ` Richard Weinberger
2025-05-12 15:33 ` Miquel Raynal
2025-05-12 15:51 ` Csókás Bence
2025-05-12 15:57 ` Richard Weinberger
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=d70952c1-e4ca-4f09-ac23-2ad13e0facc0@prolan.hu \
--to=csokas.bence@prolan.hu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=miquel.raynal@bootlin.com \
--cc=richard@nod.at \
--cc=vigneshr@ti.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