automatic DPDK test reports
 help / color / mirror / Atom feed
From: sys_stv@intel.com
To: test-report@dpdk.org, jiangheng14@huawei.com
Subject: [dpdk-test-report] |WARNING| pw(122661) sid(26685) job(PER_PATCH_BUILD6123)[[PATCH] ] linux/igb_uio: fix build with Linux 5.18
Date: 29 Jan 2023 23:37:20 -0800	[thread overview]
Message-ID: <649fab$llmfrk@fmsmga008-auth.fm.intel.com> (raw)

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


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

_apply issues_

Submitter: jiangheng (G) <jiangheng14@huawei.com>
Date: 2023-01-30 07:27:01
Reply_mail: <8b4953ef939d433f8fe19353e9ed3aa7@huawei.com>

DPDK git baseline:
	Repo:dpdk, CommitID: 2a211079a92e962bbd0ec81e425a6ffc32890e67


* Repo: dpdk
When building QAT PMD, the following issue comes up:
    
    intel-ipsec-mb.h:333: error: "AES_BLOCK_SIZE" redefined
      333 | #define AES_BLOCK_SIZE          IMB_AES_BLOCK_SIZE
    In file included from drivers/crypto/qat/qat_sym_session.c:8:
    /usr/include/openssl/aes.h:26: previous definition
--
This will be required in git-pw 2.0
error: linux/igb_uio/igb_uio.c: does not exist in index
Applying: ] linux/igb_uio: fix build with Linux 5.18
Patch failed at 0001 ] linux/igb_uio: fix build with Linux 5.18
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:[~2023-01-30  7:37 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='649fab$llmfrk@fmsmga008-auth.fm.intel.com' \
    --to=sys_stv@intel.com \
    --cc=jiangheng14@huawei.com \
    --cc=test-report@dpdk.org \
    /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).