From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id D7005A04F5 for ; Wed, 11 Dec 2019 22:29:23 +0100 (CET) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id CDDCD1D9E; Wed, 11 Dec 2019 22:29:23 +0100 (CET) Received: from us-smtp-delivery-1.mimecast.com (us-smtp-1.mimecast.com [205.139.110.61]) by dpdk.org (Postfix) with ESMTP id 30D9B1BDFD for ; Wed, 11 Dec 2019 22:29:22 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1576099761; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=7dWUnmNvR1hB7XGvTVkmSPV+/nmOg8IvWnL2lvmKILU=; b=g3lnSxaCJ7TifWwb0aGkRxMpyX+hQbviMSu9A3nSMe0Idp5GdurvR1owOHmebgmPs/lQ7c tBxeLODar6eoz83b/6vF3+pkQWpqC0xRXh+5B1tncohDF1XTLk4n0i/GrpH+Xzj9Ka0KOz 82ORvQx58ISRfSFpY9d6Jizo4a/EZFI= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-170-euVel398OyKCmXKRew3WHw-1; Wed, 11 Dec 2019 16:29:17 -0500 Received: from smtp.corp.redhat.com (int-mx07.intmail.prod.int.phx2.redhat.com [10.5.11.22]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 04627100550E; Wed, 11 Dec 2019 21:29:16 +0000 (UTC) Received: from rh.redhat.com (ovpn-116-64.ams2.redhat.com [10.36.116.64]) by smtp.corp.redhat.com (Postfix) with ESMTP id E47C510013A1; Wed, 11 Dec 2019 21:29:14 +0000 (UTC) From: Kevin Traynor To: Andrzej Ostruszka Cc: Ferruh Yigit , dpdk stable Date: Wed, 11 Dec 2019 21:26:53 +0000 Message-Id: <20191211212702.27851-61-ktraynor@redhat.com> In-Reply-To: <20191211212702.27851-1-ktraynor@redhat.com> References: <20191211212702.27851-1-ktraynor@redhat.com> MIME-Version: 1.0 X-Scanned-By: MIMEDefang 2.84 on 10.5.11.22 X-MC-Unique: euVel398OyKCmXKRew3WHw-1 X-Mimecast-Spam-Score: 0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Subject: [dpdk-stable] patch 'doc: fix tap guide' has been queued to LTS release 18.11.6 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: , Errors-To: stable-bounces@dpdk.org Sender: "stable" Hi, FYI, your patch has been queued to LTS release 18.11.6 Note it hasn't been pushed to http://dpdk.org/browse/dpdk-stable yet. It will be pushed if I get no objections before 12/17/19. 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 rebasi= ng (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-queue This queued commit can be viewed at: https://github.com/kevintraynor/dpdk-stable-queue/commit/abb5b30ad8f71311a3= 64a1001813172102c17562 Thanks. Kevin. --- >From abb5b30ad8f71311a364a1001813172102c17562 Mon Sep 17 00:00:00 2001 From: Andrzej Ostruszka Date: Thu, 21 Nov 2019 14:27:01 +0100 Subject: [PATCH] doc: fix tap guide [ upstream commit 781088dad55b840e04e699071d443f9ecfc208b3 ] Corrected one typo and IP address according RFC5735. Fixes: de96fe68ae95 ("net/tap: add basic flow API patterns and actions") Signed-off-by: Andrzej Ostruszka Reviewed-by: Ferruh Yigit --- doc/guides/nics/tap.rst | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/doc/guides/nics/tap.rst b/doc/guides/nics/tap.rst index 14c669b7b..f21e76bba 100644 --- a/doc/guides/nics/tap.rst +++ b/doc/guides/nics/tap.rst @@ -77,5 +77,5 @@ Please change the IP addresses as you see fit. If routing is enabled on the host you can also communicate with the DPDK A= pp over the internet via a standard socket layer application as long as you -account for the protocol handing in the application. +account for the protocol handling in the application. =20 If you have a Network Stack in your DPDK application or something like it = you @@ -133,7 +133,7 @@ Examples of testpmd flow rules ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ =20 -Drop packets for destination IP 192.168.0.1:: +Drop packets for destination IP 192.0.2.1:: =20 - testpmd> flow create 0 priority 1 ingress pattern eth / ipv4 dst is 1.1= .1.1 \ + testpmd> flow create 0 priority 1 ingress pattern eth / ipv4 dst is 192= .0.2.1 \ / end actions drop / end =20 --=20 2.21.0 --- Diff of the applied patch vs upstream commit (please double-check if non-= empty: --- --- -=092019-12-11 21:24:17.476282615 +0000 +++ 0061-doc-fix-tap-guide.patch=092019-12-11 21:24:12.725650019 +0000 @@ -1 +1 @@ -From 781088dad55b840e04e699071d443f9ecfc208b3 Mon Sep 17 00:00:00 2001 +From abb5b30ad8f71311a364a1001813172102c17562 Mon Sep 17 00:00:00 2001 @@ -5,0 +6,2 @@ +[ upstream commit 781088dad55b840e04e699071d443f9ecfc208b3 ] + @@ -9 +10,0 @@ -Cc: stable@dpdk.org @@ -18 +19 @@ -index 85c7b895a..7e44f8462 100644 +index 14c669b7b..f21e76bba 100644