From: Stephen Hemminger <stephen@networkplumber.org>
To: dev@dpdk.org
Cc: Yipeng Wang <yipeng1.wang@intel.com>,
Sameh Gobriel <sameh.gobriel@intel.com>,
Bruce Richardson <bruce.richardson@intel.com>,
Vladimir Medvedkin <vladimir.medvedkin@intel.com>
Subject: Re: [PATCH v2] test: skip hash tests from other CPU
Date: Mon, 29 Dec 2025 14:07:37 -0800 [thread overview]
Message-ID: <20251229140737.6bed7d22@phoenix.local> (raw)
In-Reply-To: <20251205213646.293166-1-stephen@networkplumber.org>
On Fri, 5 Dec 2025 13:36:46 -0800
Stephen Hemminger <stephen@networkplumber.org> wrote:
> When running hash tests there are lots of warnings about
> unsupported CRC32 algorithm requested. This because on x86
> it is requesting ARM algorithm and vice/versa. The fallback
> is already tested elsewhere, so can be skipped.
>
> Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
> ---
Recheck-request: iol-unit-amd64-testing
prev parent reply other threads:[~2025-12-29 22:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-05 0:25 [PATCH] " Stephen Hemminger
2025-12-05 21:36 ` [PATCH v2] " Stephen Hemminger
2025-12-29 22:07 ` Stephen Hemminger [this message]
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=20251229140737.6bed7d22@phoenix.local \
--to=stephen@networkplumber.org \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=sameh.gobriel@intel.com \
--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).