From mboxrd@z Thu Jan  1 00:00:00 1970
From: Ralph Siemsen <ralph.siemsen@linaro.org>
Date: Wed, 9 Sep 2020 09:49:58 -0400
Subject: [PATCH] cmd: mem: fix range of bitflip test
In-Reply-To: <02a9c2e2-230d-0c83-2629-8d8d8ab7218a@denx.de>
References: <20200305062132.22932-4-sr@denx.de>
 <20200909013325.6053-1-ralph.siemsen@linaro.org>
 <9c12ad86-531d-8487-997d-fc2edeab4fb4@denx.de>
 <20200909130611.GA12853@maple.netwinder.org>
 <02a9c2e2-230d-0c83-2629-8d8d8ab7218a@denx.de>
Message-ID: <20200909134958.GA30752@maple.netwinder.org>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

Hi Stefan,

On Wed, Sep 09, 2020 at 03:34:35PM +0200, Stefan Roese wrote:
>
>I agree that it's too time consuming (usually) for a manufacturing test.
>Either you are okay with disabling CONFIG_SYS_ALT_MEMTEST on your board,
>which will also disable this bitflip test. Or please continue adding a
>new Kconfig option for it - which is probable the better option.

Very good, I will send a separate patch that adds a Kconfig option.

Small procedural question: Patchwork is showing state=new for both 
versions of the mtest fix [1]. Is this normal, or did I miss some step 
when posting the v2 patch?

Thanks,
Ralph

[1] http://patchwork.ozlabs.org/project/uboot/list/?submitter=76946