From: dpdklab@iol.unh.edu
To: test-report@dpdk.org
Cc: dpdk-test-reports@iol.unh.edu
Subject: |WARNING| pw130429-130431 [PATCH] [v5, 3/3] power: amd power monitor support
Date: Wed, 16 Aug 2023 12:20:24 -0700 (PDT) [thread overview]
Message-ID: <64dd2178.170a0220.c1c13.0feaSMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-testing
Test-Status: WARNING
http://dpdk.org/patch/130429
_apply patch failure_
Submitter: Sivaprasad Tummala <Sivaprasad.Tummala@amd.com>
Date: Wednesday, August 16 2023 18:59:59
Applied on: CommitID:68150b90bda5e8f81ad1b1bad82be653b1d42a81
Apply patch set 130429-130431 failed:
Checking patch lib/eal/x86/include/rte_cpuflags.h...
error: while searching for:
RTE_CPUFLAG_AVX512VP2INTERSECT, /**< AVX512 Two Register Intersection */
RTE_CPUFLAG_WAITPKG, /**< UMONITOR/UMWAIT/TPAUSE */
/* The last item */
};
error: patch failed: lib/eal/x86/include/rte_cpuflags.h:133
Checking patch lib/eal/x86/rte_cpuflags.c...
Hunk #2 succeeded at 192 (offset -3 lines).
Applying patch lib/eal/x86/include/rte_cpuflags.h with 1 reject...
Rejected hunk #1.
Applied patch lib/eal/x86/rte_cpuflags.c cleanly.
hint: Use 'git am --show-current-patch' to see the failed patch
diff a/lib/eal/x86/include/rte_cpuflags.h b/lib/eal/x86/include/rte_cpuflags.h (rejected hunks)
@@ -133,7 +133,7 @@ enum rte_cpu_flag_t {
RTE_CPUFLAG_AVX512VP2INTERSECT, /**< AVX512 Two Register Intersection */
RTE_CPUFLAG_WAITPKG, /**< UMONITOR/UMWAIT/TPAUSE */
-
+ RTE_CPUFLAG_MONITORX, /**< MONITORX */
/* The last item */
};
https://lab.dpdk.org/results/dashboard/patchsets/27359/
UNH-IOL DPDK Community Lab
reply other threads:[~2023-08-16 19:20 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=64dd2178.170a0220.c1c13.0feaSMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=dpdk-test-reports@iol.unh.edu \
--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).