From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wm1-f50.google.com (mail-wm1-f50.google.com [209.85.128.50]) by dpdk.org (Postfix) with ESMTP id 2C43F1B433 for ; Wed, 28 Nov 2018 11:11:32 +0100 (CET) Received: by mail-wm1-f50.google.com with SMTP id 125so1972917wmh.0 for ; Wed, 28 Nov 2018 02:11:32 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:date:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=d2KRNHTCzDuWrdsk5h9Q9yG1yRQM3m0DFUkzIC8krC0=; b=UAIj6wiF2zDc580Xq6y/ML9ILvsISqQmjNeRGXsoA4lARprMHCZ7J8Z6+MR1x/m65C UPW4rcb/HhuRJW3/EyO8d6FXaccYV6Dq1pYA9wISHe5g3PqVVRxZ3Q2HTkDwEHT7+8qb 2IPYtniQybCJp7pBKvHg1Qbb05Bux3rqjeF7d0gqtXeJ9ZdbCjm3hZax7B4LZqq+lNqr Q6qN81G+4/cUh4zD0R7jfu1/JjmjgLT4W5G6xpKE3pKmpP6j5zkPxUzJjfGj1LQiyeV4 TmUFeb8uJGu13NXyffF6I4lZD7Pp5rUraZ44oErQrjigpOoehP3/6+Phj/eW3s/IBF6M StCA== X-Gm-Message-State: AA+aEWaNq9CXR46aCs87wmhZ0FXKKM9mwYbbKum2jHqFh1igR0jeP+1I TT103al/9VjhG0NgcJNCei4= X-Google-Smtp-Source: AFSGD/VH/aF8Svg5pnP4aZ2UsfeJ5mIPnS5U5+WQ1fXQgbiYybeywwhGjiLsxqjGLTrNWm17K/nqOQ== X-Received: by 2002:a1c:b1d5:: with SMTP id a204mr2256915wmf.32.1543399891443; Wed, 28 Nov 2018 02:11:31 -0800 (PST) Received: from localhost ([2a01:4b00:f419:6f00:8361:8946:ba2b:d556]) by smtp.gmail.com with ESMTPSA id f2sm6327046wru.14.2018.11.28.02.11.30 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Wed, 28 Nov 2018 02:11:30 -0800 (PST) From: Luca Boccassi To: Thomas Monjalon Cc: John McNamara , dpdk stable Date: Wed, 28 Nov 2018 10:11:26 +0000 Message-Id: <20181128101126.31013-1-bluca@debian.org> X-Mailer: git-send-email 2.19.2 In-Reply-To: <20181126124916.16240-1-bluca@debian.org> References: <20181126124916.16240-1-bluca@debian.org> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Subject: [dpdk-stable] patch 'fix dpdk.org URLs' has been queued to LTS release 16.11.9 X-BeenThere: stable@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches for DPDK stable branches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Nov 2018 10:11:32 -0000 Hi, FYI, your patch has been queued to LTS release 16.11.9 Note it hasn't been pushed to http://dpdk.org/browse/dpdk-stable yet. It will be pushed if I get no objections before 11/30/18. So please shout if anyone has objections. Also note that after the patch there's a diff of the upstream commit vs the patch applied to the branch. If the code is different (ie: not only metadata diffs), due for example to a change in context or macro names, please double check it. Thanks. Luca Boccassi --- >>From ff637d47cfeee333681c487373df10de31a68f00 Mon Sep 17 00:00:00 2001 From: Thomas Monjalon Date: Mon, 26 Nov 2018 18:51:14 +0100 Subject: [PATCH] fix dpdk.org URLs [ upstream commit 43d162bc168e5c66346acf9f464495a088a5a9f0 ] The DPDK website has a new URL scheme since June 2018. Signed-off-by: Thomas Monjalon Acked-by: John McNamara --- doc/guides/contributing/documentation.rst | 4 ++-- doc/guides/contributing/patches.rst | 8 ++++---- doc/guides/cryptodevs/qat.rst | 3 +-- doc/guides/freebsd_gsg/install_from_ports.rst | 2 +- doc/guides/howto/flow_bifurcation.rst | 2 +- doc/guides/linux_gsg/nic_perf_intel_platform.rst | 2 +- doc/guides/nics/enic.rst | 2 +- 7 files changed, 11 insertions(+), 12 deletions(-) diff --git a/doc/guides/contributing/documentation.rst b/doc/guides/contributing/documentation.rst index 2cfb1a298..2545abc78 100644 --- a/doc/guides/contributing/documentation.rst +++ b/doc/guides/contributing/documentation.rst @@ -81,7 +81,7 @@ added to by the developer. * **API documentation** The API documentation explains how to use the public DPDK functions. - The `API index page `_ shows the generated API documentation with related groups of functions. + The `API index page `_ shows the generated API documentation with related groups of functions. The API documentation should be updated via Doxygen comments when new functions are added. @@ -669,7 +669,7 @@ The following are some guidelines for use of Doxygen in the DPDK API documentati */ In the API documentation the functions will be rendered as links, see the - `online section of the rte_ethdev.h docs `_ that contains the above text. + `online section of the rte_ethdev.h docs `_ that contains the above text. * The ``@see`` keyword can be used to create a *see also* link to another file or library. This directive should be placed on one line at the bottom of the documentation section. diff --git a/doc/guides/contributing/patches.rst b/doc/guides/contributing/patches.rst index 729aea717..db851b51f 100644 --- a/doc/guides/contributing/patches.rst +++ b/doc/guides/contributing/patches.rst @@ -22,9 +22,9 @@ The DPDK development process has the following features: * Patches are reviewed publicly on the mailing list. * Successfully reviewed patches are merged to the master branch of the repository. -The mailing list for DPDK development is `dev@dpdk.org `_. -Contributors will need to `register for the mailing list `_ in order to submit patches. -It is also worth registering for the DPDK `Patchwork `_ +The mailing list for DPDK development is `dev@dpdk.org `_. +Contributors will need to `register for the mailing list `_ in order to submit patches. +It is also worth registering for the DPDK `Patchwork `_ The development process requires some familiarity with the ``git`` version control system. Refer to the `Pro Git Book `_ for further information. @@ -347,7 +347,7 @@ If the patch is in relation to a previous email thread you can add it to the sam git send-email --to dev@dpdk.org --in-reply-to <1234-foo@bar.com> 000*.patch The Message ID can be found in the raw text of emails or at the top of each Patchwork patch, -`for example `_. +`for example `_. Shallow threading (``--thread --no-chain-reply-to``) is preferred for a patch series. Once submitted your patches will appear on the mailing list and in Patchwork. diff --git a/doc/guides/cryptodevs/qat.rst b/doc/guides/cryptodevs/qat.rst index 2173819e5..c46a62eaf 100644 --- a/doc/guides/cryptodevs/qat.rst +++ b/doc/guides/cryptodevs/qat.rst @@ -89,7 +89,7 @@ To use the DPDK QAT PMD an SRIOV-enabled QAT kernel driver is required. The VF devices exposed by this driver will be used by QAT PMD. To enable QAT in DPDK, follow the instructions mentioned in -http://dpdk.org/doc/guides/linux_gsg/build_dpdk.html +http://doc.dpdk.org/guides/linux_gsg/build_dpdk.html Quick instructions as follows: @@ -107,7 +107,6 @@ For **Intel QuickAssist Technology C62x** and **Intel QuickAssist Technology C3x device, kernel 4.5 or greater is needed. See instructions for `Installation using kernel.org driver`_ below. - Installation using 01.org QAT driver ------------------------------------ diff --git a/doc/guides/freebsd_gsg/install_from_ports.rst b/doc/guides/freebsd_gsg/install_from_ports.rst index 817702911..44bbdfef6 100644 --- a/doc/guides/freebsd_gsg/install_from_ports.rst +++ b/doc/guides/freebsd_gsg/install_from_ports.rst @@ -89,7 +89,7 @@ environmental variables should be set as below: .. note:: To install a copy of the DPDK compiled using gcc, please download the - official DPDK package from http://dpdk.org/ and install manually using + official DPDK package from http://core.dpdk.org/download/ and install manually using the instructions given in the next chapter, :ref:`building_from_source` An example application can therefore be copied to a user's home directory and diff --git a/doc/guides/howto/flow_bifurcation.rst b/doc/guides/howto/flow_bifurcation.rst index 0d7226ae6..cf5d69420 100644 --- a/doc/guides/howto/flow_bifurcation.rst +++ b/doc/guides/howto/flow_bifurcation.rst @@ -296,4 +296,4 @@ The typical procedure to achieve this is as follows: 'not involved', while ``00`` or no mask means 'involved'. * For more details of the configuration, refer to the - `cloud filter test plan `_ + `cloud filter test plan `_ diff --git a/doc/guides/linux_gsg/nic_perf_intel_platform.rst b/doc/guides/linux_gsg/nic_perf_intel_platform.rst index d4a83624e..e6cf1b94a 100644 --- a/doc/guides/linux_gsg/nic_perf_intel_platform.rst +++ b/doc/guides/linux_gsg/nic_perf_intel_platform.rst @@ -64,7 +64,7 @@ This aligns with the previous output which showed that each channel has one memo Network Interface Card Requirements ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -Use a `DPDK supported `_ high end NIC such as the Intel XL710 40GbE. +Use a `DPDK supported `_ high end NIC such as the Intel XL710 40GbE. Make sure each NIC has been flashed the latest version of NVM/firmware. diff --git a/doc/guides/nics/enic.rst b/doc/guides/nics/enic.rst index 36e6f070e..7738829e6 100644 --- a/doc/guides/nics/enic.rst +++ b/doc/guides/nics/enic.rst @@ -39,7 +39,7 @@ How to obtain ENIC PMD integrated DPDK -------------------------------------- ENIC PMD support is integrated into the DPDK suite. dpdk-.tar.gz -should be downloaded from http://dpdk.org +should be downloaded from http://core.dpdk.org/download/ Configuration information -- 2.19.2 --- Diff of the applied patch vs upstream commit (please double-check if non-empty: --- --- - 2018-11-28 10:11:04.149106304 +0000 +++ 0001-fix-dpdk.org-URLs.patch 2018-11-28 10:11:04.127868924 +0000 @@ -1,134 +1,29 @@ -From 43d162bc168e5c66346acf9f464495a088a5a9f0 Mon Sep 17 00:00:00 2001 +From ff637d47cfeee333681c487373df10de31a68f00 Mon Sep 17 00:00:00 2001 From: Thomas Monjalon Date: Mon, 26 Nov 2018 18:51:14 +0100 Subject: [PATCH] fix dpdk.org URLs -The DPDK website has a new URL scheme since June 2018. +[ upstream commit 43d162bc168e5c66346acf9f464495a088a5a9f0 ] -Cc: stable@dpdk.org +The DPDK website has a new URL scheme since June 2018. Signed-off-by: Thomas Monjalon Acked-by: John McNamara --- - app/test-eventdev/test_order_atq.c | 2 +- - app/test-eventdev/test_order_queue.c | 2 +- - app/test-eventdev/test_perf_atq.c | 2 +- - app/test-eventdev/test_perf_queue.c | 2 +- - app/test-eventdev/test_pipeline_atq.c | 2 +- - app/test-eventdev/test_pipeline_queue.c | 2 +- - doc/build-sdk-meson.txt | 2 +- - doc/guides/contributing/documentation.rst | 4 ++-- - doc/guides/contributing/patches.rst | 14 +++++++------- - doc/guides/contributing/stable.rst | 6 +++--- - doc/guides/cryptodevs/qat.rst | 4 ++-- - doc/guides/freebsd_gsg/install_from_ports.rst | 2 +- - doc/guides/howto/flow_bifurcation.rst | 2 +- - doc/guides/linux_gsg/nic_perf_intel_platform.rst | 2 +- - doc/guides/nics/enic.rst | 2 +- - doc/guides/prog_guide/cryptodev_lib.rst | 2 +- - doc/guides/prog_guide/event_timer_adapter.rst | 4 ++-- - doc/guides/prog_guide/switch_representation.rst | 4 ++-- - doc/guides/rel_notes/release_18_05.rst | 10 +++++----- - doc/guides/tools/testbbdev.rst | 3 ++- - license/exceptions.txt | 2 +- - 21 files changed, 38 insertions(+), 37 deletions(-) + doc/guides/contributing/documentation.rst | 4 ++-- + doc/guides/contributing/patches.rst | 8 ++++---- + doc/guides/cryptodevs/qat.rst | 3 +-- + doc/guides/freebsd_gsg/install_from_ports.rst | 2 +- + doc/guides/howto/flow_bifurcation.rst | 2 +- + doc/guides/linux_gsg/nic_perf_intel_platform.rst | 2 +- + doc/guides/nics/enic.rst | 2 +- + 7 files changed, 11 insertions(+), 12 deletions(-) -diff --git a/app/test-eventdev/test_order_atq.c b/app/test-eventdev/test_order_atq.c -index 35debcfdc..4a8546e7f 100644 ---- a/app/test-eventdev/test_order_atq.c -+++ b/app/test-eventdev/test_order_atq.c -@@ -7,7 +7,7 @@ - - #include "test_order_common.h" - --/* See http://dpdk.org/doc/guides/tools/testeventdev.html for test details */ -+/* See http://doc.dpdk.org/guides/tools/testeventdev.html for test details */ - - static inline __attribute__((always_inline)) void - order_atq_process_stage_0(struct rte_event *const ev) -diff --git a/app/test-eventdev/test_order_queue.c b/app/test-eventdev/test_order_queue.c -index 17f7b9845..a272c7a57 100644 ---- a/app/test-eventdev/test_order_queue.c -+++ b/app/test-eventdev/test_order_queue.c -@@ -7,7 +7,7 @@ - - #include "test_order_common.h" - --/* See http://dpdk.org/doc/guides/tools/testeventdev.html for test details */ -+/* See http://doc.dpdk.org/guides/tools/testeventdev.html for test details */ - - static inline __attribute__((always_inline)) void - order_queue_process_stage_0(struct rte_event *const ev) -diff --git a/app/test-eventdev/test_perf_atq.c b/app/test-eventdev/test_perf_atq.c -index 9715a2ce8..b76ca605b 100644 ---- a/app/test-eventdev/test_perf_atq.c -+++ b/app/test-eventdev/test_perf_atq.c -@@ -4,7 +4,7 @@ - - #include "test_perf_common.h" - --/* See http://dpdk.org/doc/guides/tools/testeventdev.html for test details */ -+/* See http://doc.dpdk.org/guides/tools/testeventdev.html for test details */ - - static inline int - atq_nb_event_queues(struct evt_options *opt) -diff --git a/app/test-eventdev/test_perf_queue.c b/app/test-eventdev/test_perf_queue.c -index 04ce94192..8efdec6f9 100644 ---- a/app/test-eventdev/test_perf_queue.c -+++ b/app/test-eventdev/test_perf_queue.c -@@ -4,7 +4,7 @@ - - #include "test_perf_common.h" - --/* See http://dpdk.org/doc/guides/tools/testeventdev.html for test details */ -+/* See http://doc.dpdk.org/guides/tools/testeventdev.html for test details */ - - static inline int - perf_queue_nb_event_queues(struct evt_options *opt) -diff --git a/app/test-eventdev/test_pipeline_atq.c b/app/test-eventdev/test_pipeline_atq.c -index c60635bf6..fc4cb3bb7 100644 ---- a/app/test-eventdev/test_pipeline_atq.c -+++ b/app/test-eventdev/test_pipeline_atq.c -@@ -5,7 +5,7 @@ - - #include "test_pipeline_common.h" - --/* See http://dpdk.org/doc/guides/tools/testeventdev.html for test details */ -+/* See http://doc.dpdk.org/guides/tools/testeventdev.html for test details */ - - static __rte_always_inline int - pipeline_atq_nb_event_queues(struct evt_options *opt) -diff --git a/app/test-eventdev/test_pipeline_queue.c b/app/test-eventdev/test_pipeline_queue.c -index 25217008c..e35e9eb4c 100644 ---- a/app/test-eventdev/test_pipeline_queue.c -+++ b/app/test-eventdev/test_pipeline_queue.c -@@ -5,7 +5,7 @@ - - #include "test_pipeline_common.h" - --/* See http://dpdk.org/doc/guides/tools/testeventdev.html for test details */ -+/* See http://doc.dpdk.org/guides/tools/testeventdev.html for test details */ - - static __rte_always_inline int - pipeline_queue_nb_event_queues(struct evt_options *opt) -diff --git a/doc/build-sdk-meson.txt b/doc/build-sdk-meson.txt -index a4dd09194..29a8bd387 100644 ---- a/doc/build-sdk-meson.txt -+++ b/doc/build-sdk-meson.txt -@@ -4,7 +4,7 @@ INSTALLING DPDK USING THE MESON BUILD SYSTEM - NOTE: Compiling and installing DPDK using ``meson`` and ``ninja``, rather - than using ``make`` (GNU make) is EXPERIMENTAL. Official builds of DPDK - should always be done using ``make``, as described in the ``Getting Started --Guide`` documentation, and at "http://dpdk.org/doc/quick-start". -+Guide`` documentation, and at "http://core.dpdk.org/doc/quick-start". - - Summary - -------- diff --git a/doc/guides/contributing/documentation.rst b/doc/guides/contributing/documentation.rst -index 0165990ed..c28a95c34 100644 +index 2cfb1a298..2545abc78 100644 --- a/doc/guides/contributing/documentation.rst +++ b/doc/guides/contributing/documentation.rst -@@ -83,7 +83,7 @@ added to by the developer. +@@ -81,7 +81,7 @@ added to by the developer. * **API documentation** The API documentation explains how to use the public DPDK functions. @@ -137,7 +32,7 @@ The API documentation should be updated via Doxygen comments when new functions are added. -@@ -653,7 +653,7 @@ The following are some guidelines for use of Doxygen in the DPDK API documentati +@@ -669,7 +669,7 @@ The following are some guidelines for use of Doxygen in the DPDK API documentati */ In the API documentation the functions will be rendered as links, see the @@ -147,12 +42,12 @@ * The ``@see`` keyword can be used to create a *see also* link to another file or library. This directive should be placed on one line at the bottom of the documentation section. diff --git a/doc/guides/contributing/patches.rst b/doc/guides/contributing/patches.rst -index ffeb50436..a64bb0368 100644 +index 729aea717..db851b51f 100644 --- a/doc/guides/contributing/patches.rst +++ b/doc/guides/contributing/patches.rst -@@ -28,9 +28,9 @@ The DPDK development process has the following features: - * All sub-repositories are merged into main repository for ``-rc1`` and ``-rc2`` versions of the release. - * After the ``-rc2`` release all patches should target the main repository. +@@ -22,9 +22,9 @@ The DPDK development process has the following features: + * Patches are reviewed publicly on the mailing list. + * Successfully reviewed patches are merged to the master branch of the repository. -The mailing list for DPDK development is `dev@dpdk.org `_. -Contributors will need to `register for the mailing list `_ in order to submit patches. @@ -163,34 +58,7 @@ The development process requires some familiarity with the ``git`` version control system. Refer to the `Pro Git Book `_ for further information. -@@ -130,7 +130,7 @@ main repository:: - git clone git://dpdk.org/dpdk - git clone http://dpdk.org/git/dpdk - --sub-repositories (`list `_):: -+sub-repositories (`list `_):: - - git clone git://dpdk.org/next/dpdk-next-* - git clone http://dpdk.org/git/next/dpdk-next-* -@@ -286,7 +286,7 @@ in the body of the commit message. For example:: - Signed-off-by: Alex Smith - - --`Bugzilla `_ -+`Bugzilla `_ - is a bug- or issue-tracking system. - Bug-tracking systems allow individual or groups of developers - effectively to keep track of outstanding problems with their product. -@@ -308,7 +308,7 @@ Patch for Stable Releases - ~~~~~~~~~~~~~~~~~~~~~~~~~ - - All fix patches to the master branch that are candidates for backporting --should also be CCed to the `stable@dpdk.org `_ -+should also be CCed to the `stable@dpdk.org `_ - mailing list. - In the commit message body the Cc: stable@dpdk.org should be inserted as follows:: - -@@ -509,7 +509,7 @@ If the patch is in relation to a previous email thread you can add it to the sam +@@ -347,7 +347,7 @@ If the patch is in relation to a previous email thread you can add it to the sam git send-email --to dev@dpdk.org --in-reply-to <1234-foo@bar.com> 000*.patch The Message ID can be found in the raw text of emails or at the top of each Patchwork patch, @@ -199,59 +67,32 @@ Shallow threading (``--thread --no-chain-reply-to``) is preferred for a patch series. Once submitted your patches will appear on the mailing list and in Patchwork. -diff --git a/doc/guides/contributing/stable.rst b/doc/guides/contributing/stable.rst -index 1746c0461..2ac4f0a88 100644 ---- a/doc/guides/contributing/stable.rst -+++ b/doc/guides/contributing/stable.rst -@@ -96,7 +96,7 @@ The Stable and LTS release are coordinated on the stable@dpdk.org mailing - list. - - All fix patches to the master branch that are candidates for backporting --should also be CCed to the `stable@dpdk.org `_ -+should also be CCed to the `stable@dpdk.org `_ - mailing list. - - -@@ -107,10 +107,10 @@ A Stable Release will be released by: - - * Tagging the release with YY.MM.n (year, month, number). - * Uploading a tarball of the release to dpdk.org. --* Sending an announcement to the `announce@dpdk.org `_ -+* Sending an announcement to the `announce@dpdk.org `_ - list. - --Stable releases are available on the `dpdk.org download page `_. -+Stable releases are available on the `dpdk.org download page `_. - - - ABI diff --git a/doc/guides/cryptodevs/qat.rst b/doc/guides/cryptodevs/qat.rst -index 1db98685a..9fb9f01d1 100644 +index 2173819e5..c46a62eaf 100644 --- a/doc/guides/cryptodevs/qat.rst +++ b/doc/guides/cryptodevs/qat.rst -@@ -7,7 +7,7 @@ Intel(R) QuickAssist (QAT) Crypto Poll Mode Driver - QAT documentation consists of three parts: - - * Details of the symmetric crypto service below. --* Details of the `compression service `_ -+* Details of the `compression service `_ - in the compressdev drivers section. - * Details of building the common QAT infrastructure and the PMDs to support the - above services. See :ref:`building_qat` below. -@@ -124,7 +124,7 @@ Configuring and Building the DPDK QAT PMDs +@@ -89,7 +89,7 @@ To use the DPDK QAT PMD an SRIOV-enabled QAT kernel driver is required. The + VF devices exposed by this driver will be used by QAT PMD. + To enable QAT in DPDK, follow the instructions mentioned in +-http://dpdk.org/doc/guides/linux_gsg/build_dpdk.html ++http://doc.dpdk.org/guides/linux_gsg/build_dpdk.html + + Quick instructions as follows: + +@@ -107,7 +107,6 @@ For **Intel QuickAssist Technology C62x** and **Intel QuickAssist Technology C3x + device, kernel 4.5 or greater is needed. + See instructions for `Installation using kernel.org driver`_ below. + +- + Installation using 01.org QAT driver + ------------------------------------ - Further information on configuring, building and installing DPDK is described --`here `_. -+`here `_. - - - Quick instructions for QAT cryptodev PMD are as follows: diff --git a/doc/guides/freebsd_gsg/install_from_ports.rst b/doc/guides/freebsd_gsg/install_from_ports.rst -index d6ce847f6..253328eb1 100644 +index 817702911..44bbdfef6 100644 --- a/doc/guides/freebsd_gsg/install_from_ports.rst +++ b/doc/guides/freebsd_gsg/install_from_ports.rst -@@ -62,7 +62,7 @@ environmental variables should be set as below: +@@ -89,7 +89,7 @@ environmental variables should be set as below: .. note:: To install a copy of the DPDK compiled using gcc, please download the @@ -261,17 +102,17 @@ An example application can therefore be copied to a user's home directory and diff --git a/doc/guides/howto/flow_bifurcation.rst b/doc/guides/howto/flow_bifurcation.rst -index bc9a0934d..eabf4d730 100644 +index 0d7226ae6..cf5d69420 100644 --- a/doc/guides/howto/flow_bifurcation.rst +++ b/doc/guides/howto/flow_bifurcation.rst -@@ -268,4 +268,4 @@ The typical procedure to achieve this is as follows: +@@ -296,4 +296,4 @@ The typical procedure to achieve this is as follows: 'not involved', while ``00`` or no mask means 'involved'. * For more details of the configuration, refer to the - `cloud filter test plan `_ + `cloud filter test plan `_ diff --git a/doc/guides/linux_gsg/nic_perf_intel_platform.rst b/doc/guides/linux_gsg/nic_perf_intel_platform.rst -index 987cd0a5a..cf5c9e0db 100644 +index d4a83624e..e6cf1b94a 100644 --- a/doc/guides/linux_gsg/nic_perf_intel_platform.rst +++ b/doc/guides/linux_gsg/nic_perf_intel_platform.rst @@ -64,7 +64,7 @@ This aligns with the previous output which showed that each channel has one memo @@ -284,10 +125,10 @@ Make sure each NIC has been flashed the latest version of NVM/firmware. diff --git a/doc/guides/nics/enic.rst b/doc/guides/nics/enic.rst -index 746d89123..bc38f51aa 100644 +index 36e6f070e..7738829e6 100644 --- a/doc/guides/nics/enic.rst +++ b/doc/guides/nics/enic.rst -@@ -14,7 +14,7 @@ How to obtain ENIC PMD integrated DPDK +@@ -39,7 +39,7 @@ How to obtain ENIC PMD integrated DPDK -------------------------------------- ENIC PMD support is integrated into the DPDK suite. dpdk-.tar.gz @@ -296,134 +137,6 @@ Configuration information -diff --git a/doc/guides/prog_guide/cryptodev_lib.rst b/doc/guides/prog_guide/cryptodev_lib.rst -index 90d01e936..8ee33c875 100644 ---- a/doc/guides/prog_guide/cryptodev_lib.rst -+++ b/doc/guides/prog_guide/cryptodev_lib.rst -@@ -1043,4 +1043,4 @@ Asymmetric Crypto Device API - ~~~~~~~~~~~~~~~~~~~~~~~~~~~~ - - The cryptodev Library API is described in the --`DPDK API Reference `_ -+`DPDK API Reference `_ -diff --git a/doc/guides/prog_guide/event_timer_adapter.rst b/doc/guides/prog_guide/event_timer_adapter.rst -index 7bbbdfe90..3b4446ee9 100644 ---- a/doc/guides/prog_guide/event_timer_adapter.rst -+++ b/doc/guides/prog_guide/event_timer_adapter.rst -@@ -5,7 +5,7 @@ Event Timer Adapter Library - =========================== - - The DPDK --`Event Device library `_ -+`Event Device library `_ - introduces an event driven programming model which presents applications with - an alternative to the polling model traditionally used in DPDK - applications. Event devices can be coupled with arbitrary components to provide -@@ -21,7 +21,7 @@ The Event Timer Adapter library is designed to interface with hardware or - software implementations of the timer mechanism; it will query an eventdev PMD - to determine which implementation should be used. The default software - implementation manages timers using the DPDK --`Timer library `_. -+`Timer library `_. - - Examples of using the API are presented in the `API Overview`_ and - `Processing Timer Expiry Events`_ sections. Code samples are abstracted and -diff --git a/doc/guides/prog_guide/switch_representation.rst b/doc/guides/prog_guide/switch_representation.rst -index f5ee516f6..e5c78c234 100644 ---- a/doc/guides/prog_guide/switch_representation.rst -+++ b/doc/guides/prog_guide/switch_representation.rst -@@ -349,7 +349,7 @@ interconnection without introducing new concepts and whole new API to - implement them. This is described in `flow API (rte_flow)`_. - - .. [6] `Generic flow API (rte_flow) -- `_ -+ `_ - - Flow API (rte_flow) - ------------------- -@@ -737,7 +737,7 @@ Examples in subsequent sections apply to hypervisor applications only and - are based on port representors **A**, **B** and **C**. - - .. [2] `Flow syntax -- `_ -+ `_ - - Associating VF 1 with Physical Port 0 - ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -diff --git a/doc/guides/rel_notes/release_18_05.rst b/doc/guides/rel_notes/release_18_05.rst -index 8dc22b011..3413d8de1 100644 ---- a/doc/guides/rel_notes/release_18_05.rst -+++ b/doc/guides/rel_notes/release_18_05.rst -@@ -594,7 +594,7 @@ Known Issues - The issue is explained in more detail, including potential workarounds, - in the Bugzilla entry referenced below. - -- Bugzilla entry: https://dpdk.org/tracker/show_bug.cgi?id=50 -+ Bugzilla entry: https://bugs.dpdk.org/show_bug.cgi?id=50 - - * **pdump is not compatible with old applications.** - -@@ -619,21 +619,21 @@ Known Issues - needs to be run per-shell session, or before every test run. This change - can also be made persistent by adding ``kern.coredump=0`` to ``/etc/sysctl.conf``. - -- Bugzilla entry: https://dpdk.org/tracker/show_bug.cgi?id=53 -+ Bugzilla entry: https://bugs.dpdk.org/show_bug.cgi?id=53 - - * **ixgbe PMD crash on hotplug detach when no VF created.** - - ixgbe PMD uninit path cause null pointer dereference because of port representor - cleanup when number of VF is zero. - -- Bugzilla entry: https://dpdk.org/tracker/show_bug.cgi?id=57 -+ Bugzilla entry: https://bugs.dpdk.org/show_bug.cgi?id=57 - - * **Bonding PMD may fail to accept new slave ports in certain conditions.** - - In certain conditions when using testpmd, - bonding may fail to register new slave ports. - -- Bugzilla entry: https://dpdk.org/tracker/show_bug.cgi?id=52. -+ Bugzilla entry: https://bugs.dpdk.org/show_bug.cgi?id=52. - - * **Unexpected performance regression in Vhost library.** - -@@ -641,7 +641,7 @@ Known Issues - drop. However, in some setups, bigger performance drops have been measured - when running micro-benchmarks. - -- Bugzilla entry: https://dpdk.org/tracker/show_bug.cgi?id=48 -+ Bugzilla entry: https://bugs.dpdk.org/show_bug.cgi?id=48 - - - Shared Library Versions -diff --git a/doc/guides/tools/testbbdev.rst b/doc/guides/tools/testbbdev.rst -index 234a64f53..5caa90239 100644 ---- a/doc/guides/tools/testbbdev.rst -+++ b/doc/guides/tools/testbbdev.rst -@@ -62,7 +62,8 @@ The following are the command-line options: - - ``-e EAL_PARAMS, --eal_params EAL_PARAMS`` - Specifies EAL arguments which are passed to the test app. For more details, -- refer to DPDK documentation at http://dpdk.org/doc. -+ refer to DPDK documentation at -+ http://doc.dpdk.org/guides/linux_gsg/linux_eal_parameters.html. - - ``-t TIMEOUT, --timeout TIMEOUT`` - Specifies timeout in seconds. If not specified timeout is set to 300 seconds. -diff --git a/license/exceptions.txt b/license/exceptions.txt -index f2ef03706..f1cfa462f 100644 ---- a/license/exceptions.txt -+++ b/license/exceptions.txt -@@ -1,7 +1,7 @@ - This file will record any exceptions in DPDK Project with respect to DPDK - IP License policy as defined in DPDK Charter available at: - -- http://dpdk.org/about/charter#ip -+ https://www.dpdk.org/charter/ - - Note that following licenses are not exceptions:- - - BSD-3-Clause -- 2.19.2