automatic DPDK test reports
 help / color / mirror / Atom feed
From: sys_stv@intel.com
To: test-report@dpdk.org, vladimir.medvedkin@intel.com
Subject: compilation|WARNING| pw(150645) sid(34490) job(PER_PATCH_BUILD14754)net/ice: fix how ice driver handles flows
Date: 30 Jan 2025 07:57:33 -0800	[thread overview]
Message-ID: <ab3bf2$38qjlh@fmviesa010-auth.fm.intel.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1249 bytes --]


Test-Label: Intel-compilation
Test-Status: WARNING
http://dpdk.org/patch/150645

_apply issues_

Submitter: Vladimir Medvedkin <vladimir.medvedkin@intel.com>
Date: 2025-01-30 15:50:11
Reply_mail: <20250130155011.2658800-1-vladimir.medvedkin@intel.com>

DPDK git baseline:
	Repo:dpdk, CommitID: 9ab5a5f30c4be9f12ddaf50aec3435986bc5a495


* Repo: dpdk
During a recent cleanup a few lines were missed which are causing
    errors on ppc64le, like the ones below:
    
    drivers/net/mlx5/mlx5_rxtx_vec_altivec.h:77:17: error: cast discards
    ‘volatile’ qualifier from pointer target type [-Werror=cast-qual]
    
    lib/eal/include/rte_common.h:557:34: warning: dereferencing type-punned
    pointer will break strict-aliasing rules [-Wstrict-aliasing]
--
This will be required in git-pw 2.0
error: drivers/net/ice/ice_generic_flow.c: does not exist in index
Applying: net/ice: fix how ice driver handles flows
Patch failed at 0001 net/ice: fix how ice driver handles flows
Use 'git am --show-current-patch' to see the failed patch
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".
DPDK STV team

                 reply	other threads:[~2025-01-30 15:57 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='ab3bf2$38qjlh@fmviesa010-auth.fm.intel.com' \
    --to=sys_stv@intel.com \
    --cc=test-report@dpdk.org \
    --cc=vladimir.medvedkin@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).