From: Peter Mamonov <pmamonov@gmail.com>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: barebox@lists.infradead.org, rhi@pengutronix.de
Subject: Re: [PATCH v2] commands: import memtester 4.3.0 from Debian GNU/Linux
Date: Thu, 29 Oct 2020 23:13:58 +0300 [thread overview]
Message-ID: <20201029201357.GA7832@chr> (raw)
In-Reply-To: <20201028094737.GZ26805@pengutronix.de>
Hi, Sascha,
On Wed, Oct 28, 2020 at 10:47:37AM +0100, Sascha Hauer wrote:
> Hi Peter,
>
> There are a few more things to fix. I just saw I never answered to your
> last mail.
> [...]
> > + errno = 0;
> > + wantbytes = (size_t) strtoull_suffix(argv[optind], 0, 0);
> > + if (errno != 0) {
> > + printf("failed to parse memory argument");
> > + return COMMAND_ERROR_USAGE;
> > + }
>
> strtoull_suffix() doesn't set errno. There is currently no way to detect
> an error from strtoull_suffix().
errno is checked throughout the original code, including this slightly modified
piece. Should I remove those checks or keep them for the sake of future errno
support?
> [...]
> > + printf(" %-20s: ", "Stuck Address");
> > + console_flush();
>
> Why did you add all these console_flush() throughout the code?
I've merely replaced `fflush(stdout)` with `console_flush()` (see the original:
https://github.com/pmamonov/barebox/blob/31fd9d18f37ed58e5e559fe2ad6686066966f86e/commands/memtester/memtester.c#L374).
I choosed to keep all those (excessive) flushes as is, since most of the output
is a progress indicator which should be displayed immediately and I wasn't sure
that some type of barebox console won't cache the output.
PS Will address other comments in the next patch.
Peter
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2020-10-29 20:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-23 21:45 Peter Mamonov
2020-10-28 9:47 ` Sascha Hauer
2020-10-29 20:13 ` Peter Mamonov [this message]
2020-10-30 9:34 ` Sascha Hauer
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=20201029201357.GA7832@chr \
--to=pmamonov@gmail.com \
--cc=barebox@lists.infradead.org \
--cc=rhi@pengutronix.de \
--cc=s.hauer@pengutronix.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