patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Kevin Traynor <ktraynor@redhat.com>
To: Harshad Narayane <harshad.suresh.narayane@intel.com>
Cc: Kamalakannan R <kamalakannan.r@intel.com>,
	Cristian Dumitrescu <cristian.dumitrescu@intel.com>,
	dpdk stable <stable@dpdk.org>
Subject: patch 'doc: fix pipeline example path in user guide' has been queued to stable release 21.11.4
Date: Thu, 30 Mar 2023 09:36:00 +0100	[thread overview]
Message-ID: <20230330083600.473876-8-ktraynor@redhat.com> (raw)
In-Reply-To: <20230330083600.473876-1-ktraynor@redhat.com>

Hi,

FYI, your patch has been queued to stable release 21.11.4

Note it hasn't been pushed to http://dpdk.org/browse/dpdk-stable yet.
It will be pushed if I get no objections before 04/02/23. 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. This will indicate if there was any rebasing
needed to apply to the stable branch. If there were code changes for rebasing
(ie: not only metadata diffs), please double check that the rebase was
correctly done.

Queued patches are on a temporary branch at:
https://github.com/kevintraynor/dpdk-stable

This queued commit can be viewed at:
https://github.com/kevintraynor/dpdk-stable/commit/1ae194289fa5b0ad0731a36ac103f7f8cccc2e65

Thanks.

Kevin

---
From 1ae194289fa5b0ad0731a36ac103f7f8cccc2e65 Mon Sep 17 00:00:00 2001
From: Harshad Narayane <harshad.suresh.narayane@intel.com>
Date: Mon, 28 Nov 2022 04:33:24 +0530
Subject: [PATCH] doc: fix pipeline example path in user guide

[ upstream commit 0ab37572614c695f3087f4edaa8e0a95d1bf4a93 ]

Updated the pipeline example path in the Sample Application User Guide.

Fixes: 29485dd07bc3 ("doc: add pipeline example user guide")

Signed-off-by: Harshad Narayane <harshad.suresh.narayane@intel.com>
Signed-off-by: Kamalakannan R <kamalakannan.r@intel.com>
Acked-by: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
---
 doc/guides/sample_app_ug/pipeline.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/doc/guides/sample_app_ug/pipeline.rst b/doc/guides/sample_app_ug/pipeline.rst
index 49d50136bc..7c86bf484a 100644
--- a/doc/guides/sample_app_ug/pipeline.rst
+++ b/doc/guides/sample_app_ug/pipeline.rst
@@ -59,5 +59,5 @@ The following is an example command to run the application configured for the VX
 .. code-block:: console
 
-    $ ./<build_dir>/examples/dpdk-pipeline -c 0x3 -- -s examples/vxlan.cli
+    $ ./<build_dir>/examples/dpdk-pipeline -c 0x3 -- -s examples/pipeline/examples/vxlan.cli
 
 The application should start successfully and display as follows:
-- 
2.39.2

---
  Diff of the applied patch vs upstream commit (please double-check if non-empty:
---
--- -	2023-03-30 09:30:45.487075298 +0100
+++ 0009-doc-fix-pipeline-example-path-in-user-guide.patch	2023-03-30 09:30:45.275229273 +0100
@@ -1 +1 @@
-From 0ab37572614c695f3087f4edaa8e0a95d1bf4a93 Mon Sep 17 00:00:00 2001
+From 1ae194289fa5b0ad0731a36ac103f7f8cccc2e65 Mon Sep 17 00:00:00 2001
@@ -5,0 +6,2 @@
+[ upstream commit 0ab37572614c695f3087f4edaa8e0a95d1bf4a93 ]
+
@@ -9 +10,0 @@
-Cc: stable@dpdk.org


      parent reply	other threads:[~2023-03-30  8:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-30  8:35 patch 'examples/qos_sched: fix config entries in wrong sections' " Kevin Traynor
2023-03-30  8:35 ` patch 'net/mlx5: fix build with GCC 12 and ASan' " Kevin Traynor
2023-03-30  8:35 ` patch 'net/mlx5: fix CQE dump for Tx' " Kevin Traynor
2023-03-30  8:35 ` patch 'net/mlx5: fix sysfs port name translation' " Kevin Traynor
2023-03-30  8:35 ` patch 'test/crypto: fix statistics error messages' " Kevin Traynor
2023-03-30  8:35 ` patch 'pdump: fix build with GCC 12' " Kevin Traynor
2023-03-30  8:35 ` patch 'acl: fix crash on PPC64 with GCC 11' " Kevin Traynor
2023-03-30  8:36 ` Kevin Traynor [this message]

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=20230330083600.473876-8-ktraynor@redhat.com \
    --to=ktraynor@redhat.com \
    --cc=cristian.dumitrescu@intel.com \
    --cc=harshad.suresh.narayane@intel.com \
    --cc=kamalakannan.r@intel.com \
    --cc=stable@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).