From: Richard Weinberger <richard@nod.at>
To: Miquel Raynal <miquel.raynal@bootlin.com>
Cc: "Rafał Miłecki" <zajec5@gmail.com>,
linux-mtd <linux-mtd@lists.infradead.org>,
"Rafał Miłecki" <rafal@milecki.pl>
Subject: Re: [PATCH mtd-utils] nandwrite: warn about writing 0xff blocks
Date: Mon, 28 Mar 2022 10:51:45 +0200 (CEST) [thread overview]
Message-ID: <598533037.192422.1648457505190.JavaMail.zimbra@nod.at> (raw)
In-Reply-To: <20220328104557.4f065c25@xps13>
----- Ursprüngliche Mail -----
> Von: "Miquel Raynal" <miquel.raynal@bootlin.com>
>> > While I like the patch I'm still not so convinced why we can't make
>> > skipallffs=true by default.
>>
>> I thought it's about changing / breaking user interface:
>>
>> [2022-03-25] [11:40:53 CET] <derRichard> mraynal: i think we should make
>> --skip-all-ffs default in nandwrite
>> [2022-03-25] [11:40:56 CET] <derRichard> what do you think?
>> [2022-03-25] [11:42:00 CET] <rmilecki> i was preparing a patch with warning if
>> any 0xff block has been written
>> [2022-03-25] [11:42:33 CET] <rmilecki> i didn't know defaulting to
>> --skip-all-ffs can be done
>> [2022-03-25] [11:47:05 CET] <mraynal> well, that would break the user interface
>
> Indeed I raised this issue but I am not opposed to this change if
> everybody agrees that it's a good move. In particular, the NAND
> sublayer will give the same "empty" data to userspace whether it
> programmed empty pages or skipped them. So I guess we are fine against
> direct regressions (but we might break clever scripts doing strange
> things).
>
> I would go for this solution:
> - Bring support for the double flag -[no-]skip-ffs
> - Make the use of -skip-ffs the default
> So that it is easy for scripting people to ensure their way is fine?
Also emit a warning that a 0xff page is being skipped if the user
no not specify anything at the command line.
Then users will notice that the default has changed.
Thanks,
//richard
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
prev parent reply other threads:[~2022-03-28 8:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-25 12:00 [PATCH mtd-utils] nandwrite: warn about writing 0xff blocks Rafał Miłecki
2022-03-28 6:51 ` David Oberhollenzer
2022-03-28 7:28 ` Richard Weinberger
2022-03-28 7:27 ` Richard Weinberger
2022-03-28 8:29 ` Rafał Miłecki
2022-03-28 8:45 ` Miquel Raynal
2022-03-28 8:51 ` Richard Weinberger [this message]
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=598533037.192422.1648457505190.JavaMail.zimbra@nod.at \
--to=richard@nod.at \
--cc=linux-mtd@lists.infradead.org \
--cc=miquel.raynal@bootlin.com \
--cc=rafal@milecki.pl \
--cc=zajec5@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 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.