From: Ralph Siemsen <ralph.siemsen@linaro.org>
To: u-boot@lists.denx.de
Subject: [PATCH] cmd: mem: fix range of bitflip test
Date: Wed, 9 Sep 2020 11:07:14 -0400 [thread overview]
Message-ID: <20200909150714.GA17036@maple.netwinder.org> (raw)
In-Reply-To: <ccd3ef45-fbe6-89d1-6e25-0f1d116fed05@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
next prev parent reply other threads:[~2020-09-09 15:07 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-05 6:21 [PATCH 1/4] cmd: mem: Correctly count the errors in mtest Stefan Roese
2020-03-05 6:21 ` [PATCH 2/4] cmd: mem: Drop eldk-4.2 workaround and use cast in unmap_sysmem() Stefan Roese
2020-04-21 12:26 ` Tom Rini
2020-03-05 6:21 ` [PATCH 3/4] cmd: mem: Use IS_ENABLED instead of alt_test variable Stefan Roese
2020-04-21 12:26 ` Tom Rini
2020-03-05 6:21 ` [PATCH 4/4] cmd: mem: Add bitflip memory test to alternate mtest Stefan Roese
2020-04-21 12:26 ` Tom Rini
2020-09-09 1:33 ` [PATCH] cmd: mem: fix range of bitflip test Ralph Siemsen
2020-09-09 8:49 ` Stefan Roese
2020-09-09 13:02 ` [PATCH v2] " Ralph Siemsen
2020-09-09 13:35 ` Stefan Roese
2020-09-09 15:21 ` [PATCH v3] " Ralph Siemsen
2020-09-09 15:30 ` Stefan Roese
2020-09-09 15:42 ` [PATCH v4] " Ralph Siemsen
2020-09-09 16:10 ` [PATCH v5] " Ralph Siemsen
2020-09-10 5:09 ` Stefan Roese
2020-09-19 12:34 ` Tom Rini
2020-09-09 13:06 ` [PATCH] " Ralph Siemsen
2020-09-09 13:34 ` Stefan Roese
2020-09-09 13:49 ` Ralph Siemsen
2020-09-09 13:53 ` Stefan Roese
2020-09-09 15:07 ` Ralph Siemsen [this message]
2020-09-09 15:13 ` Stefan Roese
2020-09-09 15:17 ` Ralph Siemsen
2020-04-21 12:26 ` [PATCH 1/4] cmd: mem: Correctly count the errors in mtest Tom Rini
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=20200909150714.GA17036@maple.netwinder.org \
--to=ralph.siemsen@linaro.org \
--cc=u-boot@lists.denx.de \
/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