From: Miquel Raynal <miquel.raynal@bootlin.com>
To: "Bjørn Mork" <bjorn@mork.no>
Cc: <Tudor.Ambarus@microchip.com>, <ezequiel@vanguardiasur.com.ar>,
<richard@nod.at>, <vigneshr@ti.com>,
<linux-mtd@lists.infradead.org>
Subject: Re: [PATCH] mtdblock: warn if opened on NAND
Date: Fri, 22 Apr 2022 11:03:51 +0200 [thread overview]
Message-ID: <20220422110351.6b5cd370@xps13> (raw)
In-Reply-To: <87wnfhmxlo.fsf@miraculix.mork.no>
Hi folks,
bjorn@mork.no wrote on Fri, 22 Apr 2022 08:38:27 +0200:
> <Tudor.Ambarus@microchip.com> writes:
>
> >> Commit e07403a8c6be is based on two false assumptions:
> >> 1) the presence of the mtdblock driver is a problem
> >
> > It is a problem. Using it will wear out parts of your raw flash relatively
> > fast.
>
> There is a significant difference between PRESENCE and USING.
>
> I'll just stop this now. You're not arguing with me but woith some
> straw man you created.
Right now there is a message for _every_ mtd device that gets created
only if mtdblock support is built-in. Of course enabling mtdblock if
you don't use it is a waste of space, but it is far less an issue than
people actually using it and I think that is our main target.
The warnings from Ezequiel were a good idea but right now I think we
all agree that they are too frequent. A single warning would be an
improvement, but otherwise a warning only when ->open() gets called
seems a good enough step forward for me.
Thanks,
Miquèl
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2022-04-22 9:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-28 16:11 [PATCH] mtdblock: warn if opened on NAND Bjørn Mork
2022-04-02 21:25 ` Ezequiel Garcia
2022-04-21 14:27 ` Tudor.Ambarus
2022-04-21 16:43 ` Bjørn Mork
2022-04-22 6:25 ` Tudor.Ambarus
2022-04-22 6:38 ` Bjørn Mork
2022-04-22 9:03 ` Miquel Raynal [this message]
2022-04-22 16:07 ` Ezequiel Garcia
2022-04-26 7:37 ` Miquel Raynal
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=20220422110351.6b5cd370@xps13 \
--to=miquel.raynal@bootlin.com \
--cc=Tudor.Ambarus@microchip.com \
--cc=bjorn@mork.no \
--cc=ezequiel@vanguardiasur.com.ar \
--cc=linux-mtd@lists.infradead.org \
--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