From: dpdklab@iol.unh.edu
To: test-report@dpdk.org
Cc: dpdk-test-reports@iol.unh.edu
Subject: |WARNING| pw114257 [PATCH] config/arm: add Graviton3
Date: Wed, 27 Jul 2022 02:49:58 -0400 (EDT) [thread overview]
Message-ID: <20220727064958.84F346D34A@noxus.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 1804 bytes --]
Test-Label: iol-testing
Test-Status: WARNING
http://dpdk.org/patch/114257
_apply patch failure_
Submitter: Ruifeng Wang <ruifeng.wang@arm.com>
Date: Wednesday, July 27 2022 06:33:21
Applied on: CommitID:72206323a5dd3182b13f61b25a64abdddfee595c
Apply patch set 114257 failed:
Checking patch config/arm/arm64_graviton3_linux_gcc...
Checking patch config/arm/meson.build...
Hunk #1 succeeded at 335 (offset 24 lines).
error: while searching for:
dpaa: NXP DPAA
emag: Ampere eMAG
graviton2: AWS Graviton2
kunpeng920: HiSilicon Kunpeng 920
kunpeng930: HiSilicon Kunpeng 930
n1sdp: Arm Neoverse N1SDP
error: patch failed: config/arm/meson.build:390
error: while searching for:
'dpaa': soc_dpaa,
'emag': soc_emag,
'graviton2': soc_graviton2,
'kunpeng920': soc_kunpeng920,
'kunpeng930': soc_kunpeng930,
'n1sdp': soc_n1sdp,
error: patch failed: config/arm/meson.build:413
Applied patch config/arm/arm64_graviton3_linux_gcc cleanly.
Applying patch config/arm/meson.build with 2 rejects...
Hunk #1 applied cleanly.
Rejected hunk #2.
Rejected hunk #3.
diff a/config/arm/meson.build b/config/arm/meson.build (rejected hunks)
@@ -390,6 +398,7 @@ cn10k: Marvell OCTEON 10
dpaa: NXP DPAA
emag: Ampere eMAG
graviton2: AWS Graviton2
+graviton3: AWS Graviton3
kunpeng920: HiSilicon Kunpeng 920
kunpeng930: HiSilicon Kunpeng 930
n1sdp: Arm Neoverse N1SDP
@@ -413,6 +422,7 @@ socs = {
'dpaa': soc_dpaa,
'emag': soc_emag,
'graviton2': soc_graviton2,
+ 'graviton3': soc_graviton3,
'kunpeng920': soc_kunpeng920,
'kunpeng930': soc_kunpeng930,
'n1sdp': soc_n1sdp,
https://lab.dpdk.org/results/dashboard/patchsets/23083/
UNH-IOL DPDK Community Lab
reply other threads:[~2022-07-27 6:50 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=20220727064958.84F346D34A@noxus.dpdklab.iol.unh.edu \
--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).