From: zhoumin <zhoumin@loongson.cn>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: yipeng1.wang@intel.com, sameh.gobriel@intel.com,
bruce.richardson@intel.com, vladimir.medvedkin@intel.com,
pablo.de.lara.guarch@intel.com, dev@dpdk.org
Subject: Re: [PATCH 1/1] test/hash: fix error log output
Date: Wed, 13 Sep 2023 17:23:52 +0800 [thread overview]
Message-ID: <47c9ab42-44b6-e6a6-1396-4b7db9ee78f3@loongson.cn> (raw)
In-Reply-To: <20230913003057.5f22f687@fedora>
On Wed, Sep 13, 2023 at 3:30PM, Stephen Hemminger wrote:
> On Tue, 12 Sep 2023 19:52:39 +0800
> Min Zhou <zhoumin@loongson.cn> wrote:
>
>> diff --git a/app/test/test_hash_readwrite.c
>> b/app/test/test_hash_readwrite.c index 74ca13912f..4997a01249 100644
>> --- a/app/test/test_hash_readwrite.c
>> +++ b/app/test/test_hash_readwrite.c
>> @@ -162,7 +162,7 @@ init_params(int use_ext, int use_htm, int rw_lf,
>> int use_jhash)
>> handle = rte_hash_create(&hash_params);
>> if (handle == NULL) {
>> - printf("hash creation failed");
>> + printf("hash creation failed\n");
> Errors should be writen to stderr, not stdout?
> It looks like the hash test doesn't do that anywhere though.
Agree! The errors should go to stderr. However, there are many such
cases in app/test that errors were written to stderr. It requires huge
effort to fix them.
Regards,
Min
next prev parent reply other threads:[~2023-09-13 9:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-12 11:52 Min Zhou
2023-09-13 7:30 ` Stephen Hemminger
2023-09-13 9:23 ` zhoumin [this message]
2023-11-23 0:44 ` Thomas Monjalon
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=47c9ab42-44b6-e6a6-1396-4b7db9ee78f3@loongson.cn \
--to=zhoumin@loongson.cn \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=pablo.de.lara.guarch@intel.com \
--cc=sameh.gobriel@intel.com \
--cc=stephen@networkplumber.org \
--cc=vladimir.medvedkin@intel.com \
--cc=yipeng1.wang@intel.com \
/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;
as well as URLs for NNTP newsgroup(s).