From: Boris Brezillon <boris.brezillon@bootlin.com>
To: Stefan Agner <stefan@agner.ch>
Cc: boris.brezillon@free-electrons.com, computersforpeace@gmail.com,
dwmw2@infradead.org, marek.vasut@gmail.com,
cyrille.pitchen@wedev4u.fr, richard@nod.at,
linux-mtd@lists.infradead.org,
David Oberhollenzer <david.oberhollenzer@sigma-star.at>
Subject: Re: [PATCH mtd-utils] mtd: tests: check erase block count in page test
Date: Sun, 4 Mar 2018 10:16:25 +0100 [thread overview]
Message-ID: <20180304101625.4cb2bdc5@bbrezillon> (raw)
In-Reply-To: <20180303223946.18636-1-stefan@agner.ch>
+David who maintains mtd-utils.
On Sat, 3 Mar 2018 23:39:46 +0100
Stefan Agner <stefan@agner.ch> wrote:
> When there is only a single erase block, the cross erase test
> does not report sensible errors. Warn in case there is only
> a single erase block instead of executing the test.
>
> Signed-off-by: Stefan Agner <stefan@agner.ch>
> ---
> tests/mtd-tests/nandpagetest.c | 8 ++++++--
> 1 file changed, 6 insertions(+), 2 deletions(-)
>
> diff --git a/tests/mtd-tests/nandpagetest.c b/tests/mtd-tests/nandpagetest.c
> index c6812df..115cedb 100644
> --- a/tests/mtd-tests/nandpagetest.c
> +++ b/tests/mtd-tests/nandpagetest.c
> @@ -551,8 +551,12 @@ int main(int argc, char **argv)
> }
> printf("verified %u eraseblocks\n", i);
>
> - if (crosstest())
> - goto out;
> + if (ebcnt > 1) {
> + if (crosstest())
> + goto out;
> + } else {
> + printf("skipping erasecrosstest, 2 erase blocks needed\n");
> + }
>
> if (erasecrosstest())
> goto out;
--
Boris Brezillon, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-03-04 9:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-03 22:39 [PATCH mtd-utils] mtd: tests: check erase block count in page test Stefan Agner
2018-03-04 9:16 ` Boris Brezillon [this message]
2018-03-05 11:27 ` David Oberhollenzer
2018-03-18 21:23 ` Boris Brezillon
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=20180304101625.4cb2bdc5@bbrezillon \
--to=boris.brezillon@bootlin.com \
--cc=boris.brezillon@free-electrons.com \
--cc=computersforpeace@gmail.com \
--cc=cyrille.pitchen@wedev4u.fr \
--cc=david.oberhollenzer@sigma-star.at \
--cc=dwmw2@infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=marek.vasut@gmail.com \
--cc=richard@nod.at \
--cc=stefan@agner.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox