[PATCH] cmd: mem: fix range of bitflip test

[Stefan Roese]

Hi Ralph,

On 09.09.20 17:07, Ralph Siemsen wrote:
> 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.

Okay.

>>> 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?

Usually the RB is only added, when not too many further changes are
made by the committer. There is no strict rule here AFAIK.

>> You could mark your v1 as superseded in patchwork though.
> 
> Seems somebody beat me to it, v1 is now marked as superseded.

Tom is quite active here. ;)

Thanks,
Stefan