From: qemudev@loongson.cn
To: test-report@dpdk.org
Cc: Fengnan Chang <changfengnan@bytedance.com>, zhoumin@loongson.cn
Subject: |WARNING| pw125187 [PATCH 21.11] eal: cleanup alarm and hotplug before memory detach
Date: Thu, 16 Mar 2023 19:34:57 +0800 [thread overview]
Message-ID: <202303161134.32GBYv8r264470@localhost.localdomain> (raw)
In-Reply-To: <20230316114818.99552-1-changfengnan@bytedance.com>
Test-Label: loongarch-compilation
Test-Status: WARNING
http://dpdk.org/patch/125187
_apply patch failure_
Submitter: Fengnan Chang <changfengnan@bytedance.com>
Date: Thu, 16 Mar 2023 19:48:18 +0800
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 069fd1204b818b0d40f26e6395cb7b7ce1bb1db4
Apply patch set 125187 failed:
Checking patch lib/eal/freebsd/eal.c...
error: while searching for:
rte_mp_channel_cleanup();
rte_trace_save();
eal_trace_fini();
/* after this point, any DPDK pointers will become dangling */
rte_eal_memory_detach();
rte_eal_alarm_cleanup();
eal_cleanup_config(internal_conf);
return 0;
}
error: patch failed: lib/eal/freebsd/eal.c:988
error: lib/eal/freebsd/eal.c: patch does not apply
Checking patch lib/eal/linux/eal.c...
error: while searching for:
rte_mp_channel_cleanup();
rte_trace_save();
eal_trace_fini();
/* after this point, any DPDK pointers will become dangling */
rte_eal_memory_detach();
rte_eal_alarm_cleanup();
eal_cleanup_config(internal_conf);
return 0;
}
error: patch failed: lib/eal/linux/eal.c:1370
error: lib/eal/linux/eal.c: patch does not apply
next parent reply other threads:[~2023-03-16 11:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230316114818.99552-1-changfengnan@bytedance.com>
2023-03-16 11:34 ` qemudev [this message]
2023-03-16 11:49 ` checkpatch
2023-03-16 12:47 |WARNING| pw125187 [PATCH] [21.11] " dpdklab
2023-03-16 13:19 dpdklab
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=202303161134.32GBYv8r264470@localhost.localdomain \
--to=qemudev@loongson.cn \
--cc=changfengnan@bytedance.com \
--cc=test-report@dpdk.org \
--cc=zhoumin@loongson.cn \
/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).