From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ralph Siemsen Date: Wed, 9 Sep 2020 11:07:14 -0400 Subject: [PATCH] cmd: mem: fix range of bitflip test In-Reply-To: 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> <20200909134958.GA30752@maple.netwinder.org> Message-ID: <20200909150714.GA17036@maple.netwinder.org> List-Id: 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:53:08PM +0200, Stefan Roese wrote: >Hi Ralph, > >On 09.09.20 15:49, Ralph Siemsen wrote: >> >>Very good, I will send a separate patch that adds a Kconfig option. As it turns out, doing a separate patch for this gets messy, and also would introduce a dependency between the patches. Will do v3 instead. >>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? > >The only thing you missed, was adding my RB tag to v2. I did send a new >RB again to this mail, so patchwork will collect it automatically. Thanks, I was not entirely clear what the policy was for this. Presumably there is a way for a reviewer to 'revoke' the RB in case they disagree with subsequent changes? >You could mark your v1 as superseded in patchwork though. Seems somebody beat me to it, v1 is now marked as superseded. Ralph