From: Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>
To: stable@dpdk.org
Cc: Tal Shnaiderman <talshn@nvidia.com>,
Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>,
Yu Jiang <yux.jiang@intel.com>
Subject: [dpdk-stable] [PATCH 19.11] eal/windows: add cleanup function stub
Date: Mon, 14 Jun 2021 00:36:02 +0300 [thread overview]
Message-ID: <20210613213602.23843-1-dmitry.kozliuk@gmail.com> (raw)
Upstream commit 10aa375704c1 ("examples: add eal cleanup to examples")
requires librte_eal to export rte_eal_clearnup(). On Windows, it was
exported by commit c91717eb75c8 ("eal/windows: support exit and panic"),
which is based on refactoring that is not backported.
Add a stub to fix the build.
In 19.11 LTS this function has nothing to clean up.
Bugzilla ID: 732
Reported-by: Yu Jiang <yux.jiang@intel.com>
Signed-off-by: Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>
---
lib/librte_eal/rte_eal_exports.def | 1 +
lib/librte_eal/windows/eal/eal.c | 6 ++++++
2 files changed, 7 insertions(+)
diff --git a/lib/librte_eal/rte_eal_exports.def b/lib/librte_eal/rte_eal_exports.def
index c1bdee1c40..61b4082a54 100644
--- a/lib/librte_eal/rte_eal_exports.def
+++ b/lib/librte_eal/rte_eal_exports.def
@@ -1,5 +1,6 @@
EXPORTS
__rte_panic
+ rte_eal_cleanup
rte_eal_init
rte_eal_mp_remote_launch
rte_eal_mp_wait_lcore
diff --git a/lib/librte_eal/windows/eal/eal.c b/lib/librte_eal/windows/eal/eal.c
index ce460481f8..7cfa8451a3 100644
--- a/lib/librte_eal/windows/eal/eal.c
+++ b/lib/librte_eal/windows/eal/eal.c
@@ -82,3 +82,9 @@ rte_eal_init(int argc __rte_unused, char **argv __rte_unused)
rte_eal_mp_wait_lcore();
return 0;
}
+
+int
+rte_eal_cleanup(void)
+{
+ return 0;
+}
--
2.29.3
next reply other threads:[~2021-06-13 21:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-13 21:36 Dmitry Kozlyuk [this message]
2021-06-14 5:23 ` Christian Ehrhardt
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=20210613213602.23843-1-dmitry.kozliuk@gmail.com \
--to=dmitry.kozliuk@gmail.com \
--cc=stable@dpdk.org \
--cc=talshn@nvidia.com \
--cc=yux.jiang@intel.com \
/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).