From: sys_stv@intel.com
To: test-report@dpdk.org, rma.ma@jaguarmicro.com
Subject: compilation|WARNING| pw(129439) sid(28899) job(PER_PATCH_BUILD8322)回复: [PATCH v3] vhost: add notify reply ops to fix message deadlock
Date: 11 Jul 2023 02:33:03 -0700 [thread overview]
Message-ID: <8899fd$k06lhu@orsmga003-auth.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1199 bytes --]
Test-Label: Intel-compilation
Test-Status: WARNING
http://dpdk.org/patch/129439
_apply issues_
Submitter: Rma Ma <rma.ma@jaguarmicro.com>
Date: 2023-07-11 09:25:25
Reply_mail: <PUZPR06MB47423251E6A4BBCA6B9FEDA39931A@PUZPR06MB4742.apcprd06.prod.outlook.com>
DPDK git baseline:
Repo:dpdk-next-virtio, CommitID: 025280d219fcfe79b558c2470c7fabc7014ef5a2
Repo:dpdk, CommitID: 623dc9364dc6a818799941cc26dc8f70feb2bb24
* Repo: dpdk-next-virtio
Adds braces around initializer to resolve the following
false-positive build error with gcc 4.8.5 on CentOS:
lib/vhost/vduse.c:441:9: error: missing braces around initializer
[-Werror=missing-braces]
Fixes: 653327e191f0 ("vhost: add multiqueue support to VDUSE")
Cc: maxime.coquelin@redhat.com
--
You should provide the server version in the URL configured via git-config or --server
This will be required in git-pw 2.0
error: cannot convert from eucgb2312_cn to UTF-8
fatal: could not parse patch
* Repo: dpdk
You should provide the server version in the URL configured via git-config or --server
This will be required in git-pw 2.0
error: cannot convert from eucgb2312_cn to UTF-8
fatal: could not parse patch
DPDK STV team
reply other threads:[~2023-07-11 9:33 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='8899fd$k06lhu@orsmga003-auth.jf.intel.com' \
--to=sys_stv@intel.com \
--cc=rma.ma@jaguarmicro.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).