From: "Juraj Linkeš" <juraj.linkes@pantheon.tech>
To: thomas@monjalon.net, david.marchand@redhat.com,
Honnappa.Nagarahalli@arm.com, ohilyard@iol.unh.edu,
lijuan.tu@intel.com
Cc: dev@dpdk.org, "Juraj Linkeš" <juraj.linkes@pantheon.tech>
Subject: [RFC PATCH v1 3/8] dts: merge DTS requirements.txt to DPDK
Date: Wed, 6 Apr 2022 15:31:46 +0000 [thread overview]
Message-ID: <20220406153151.2917346-4-juraj.linkes@pantheon.tech> (raw)
In-Reply-To: <20220406153151.2917346-1-juraj.linkes@pantheon.tech>
---
dts/requirements.txt | 42 ++++++++++++++++++++++++++++++++++++++++++
1 file changed, 42 insertions(+)
create mode 100644 dts/requirements.txt
diff --git a/dts/requirements.txt b/dts/requirements.txt
new file mode 100644
index 0000000000..f58a64defa
--- /dev/null
+++ b/dts/requirements.txt
@@ -0,0 +1,42 @@
+# BSD LICENSE
+#
+# Copyright(c) 2019 Intel Corporation. All rights reserved.
+# All rights reserved.
+#
+# Redistribution and use in source and binary forms, with or without
+# modification, are permitted provided that the following conditions
+# are met:
+#
+# * Redistributions of source code must retain the above copyright
+# notice, this list of conditions and the following disclaimer.
+# * Redistributions in binary form must reproduce the above copyright
+# notice, this list of conditions and the following disclaimer in
+# the documentation and/or other materials provided with the
+# distribution.
+# * Neither the name of Intel Corporation nor the names of its
+# contributors may be used to endorse or promote products derived
+# from this software without specific prior written permission.
+#
+# THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
+# "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
+# LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
+# A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
+# OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
+# SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
+# LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
+# DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
+# THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
+# (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
+# OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+
+
+xlwt==1.3.0
+pexpect==4.7.0
+numpy==1.18.5
+docutils
+pcapy
+xlrd
+scapy==2.4.4
+threadpool
+isort
+texttable
\ No newline at end of file
--
2.20.1
next prev parent reply other threads:[~2022-04-06 15:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-06 15:31 [RFC PATCH v1 0/8] merge DTS repo config and tools " Juraj Linkeš
2022-04-06 15:31 ` [RFC PATCH v1 1/8] dts: merge DTS format.sh " Juraj Linkeš
2022-04-06 15:31 ` [RFC PATCH v1 2/8] dts: merge DTS pyproject.toml " Juraj Linkeš
2022-04-06 15:31 ` Juraj Linkeš [this message]
2022-04-06 15:31 ` [RFC PATCH v1 4/8] dts: merge DTS vm_images/Dockerfile " Juraj Linkeš
2022-04-06 15:31 ` [RFC PATCH v1 5/8] dts: merge DTS vm_images/README.md " Juraj Linkeš
2022-04-06 15:31 ` [RFC PATCH v1 6/8] dts: merge DTS vm_images/create_vm_image.py " Juraj Linkeš
2022-04-06 15:31 ` [RFC PATCH v1 7/8] dts: merge DTS vm_images/make_build_container.sh " Juraj Linkeš
2022-04-06 15:31 ` [RFC PATCH v1 8/8] dts: merge DTS vm_images/network-init.sh " Juraj Linkeš
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=20220406153151.2917346-4-juraj.linkes@pantheon.tech \
--to=juraj.linkes@pantheon.tech \
--cc=Honnappa.Nagarahalli@arm.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=lijuan.tu@intel.com \
--cc=ohilyard@iol.unh.edu \
--cc=thomas@monjalon.net \
/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).