From mboxrd@z Thu Jan 1 00:00:00 1970
Return-Path: <dev-bounces@dpdk.org>
Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124])
by inbox.dpdk.org (Postfix) with ESMTP id D7576A0554;
Fri, 10 Jun 2022 17:35:59 +0200 (CEST)
Received: from [217.70.189.124] (localhost [127.0.0.1])
by mails.dpdk.org (Postfix) with ESMTP id EB8604281C;
Fri, 10 Jun 2022 17:35:55 +0200 (CEST)
Received: from mga04.intel.com (mga04.intel.com [192.55.52.120])
by mails.dpdk.org (Postfix) with ESMTP id 09AD7427E9
for <dev@dpdk.org>; Fri, 10 Jun 2022 17:35:53 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple;
d=intel.com; i=@intel.com; q=dns/txt; s=Intel;
t=1654875354; x=1686411354;
h=from:to:cc:subject:date:message-id:in-reply-to:
references:mime-version:content-transfer-encoding;
bh=iIFowQeY5w+yqQK7OFLvFaOBPn9gpcs+dM5C9cBqPq8=;
b=OutOysvirldQ+1Kn3QCPfXzBriKM6j/D8+FfWP2LoqQzfWCUyz4srJbb
rWq9ZGQYq0Y+jXGBbnf4dk8Si61MGWNxvCIuX8o22biegry1P9PERiaE7
ry++73xpMJ3u3Pn1NuGEyYcR2AlBfY5AvfrRcsals/vK80Mg/6K9U3+Io
8HHkDzlatbvuIwn3v3BQE3pjFLmFfRROqKHQMDu9yQu2/hX9kxZ4NrZCN
W7WrDNf+CAcre9m14uMSV3pD+E5GZ/YyyiB0qpF/NhKZgYdaMe3CY2U7u
4SipPZd6S5Uho/A86IdtEubRCDzocdgLmUcfP7Cy0pmMa4+qpq77bZ6OW g==;
X-IronPort-AV: E=McAfee;i="6400,9594,10374"; a="276439902"
X-IronPort-AV: E=Sophos;i="5.91,290,1647327600"; d="scan'208";a="276439902"
Received: from orsmga008.jf.intel.com ([10.7.209.65])
by fmsmga104.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384;
10 Jun 2022 08:35:52 -0700
X-ExtLoop1: 1
X-IronPort-AV: E=Sophos;i="5.91,290,1647327600"; d="scan'208";a="610761244"
Received: from silpixa00401385.ir.intel.com (HELO
silpixa00401385.ger.corp.intel.com.) ([10.237.223.181])
by orsmga008.jf.intel.com with ESMTP; 10 Jun 2022 08:35:50 -0700
From: Bruce Richardson <bruce.richardson@intel.com>
To: dev@dpdk.org
Cc: Maxime Coquelin <maxime.coquelin@redhat.com>,
Chenbo Xia <chenbo.xia@intel.com>,
Bruce Richardson <bruce.richardson@intel.com>
Subject: [PATCH v3 2/4] doc/howto: rename files to match new content name
Date: Fri, 10 Jun 2022 16:35:33 +0100
Message-Id: <20220610153535.659076-3-bruce.richardson@intel.com>
X-Mailer: git-send-email 2.34.1
In-Reply-To: <20220610153535.659076-1-bruce.richardson@intel.com>
References: <20220527162659.129022-1-bruce.richardson@intel.com>
<20220610153535.659076-1-bruce.richardson@intel.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: DPDK patches and discussions <dev.dpdk.org>
List-Unsubscribe: <https://mails.dpdk.org/options/dev>,
<mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://mails.dpdk.org/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <https://mails.dpdk.org/listinfo/dev>,
<mailto:dev-request@dpdk.org?subject=subscribe>
Errors-To: dev-bounces@dpdk.org
Since the section in the "howto" has been renamed from "exceptional
path" to "exception path", we can rename the relevant files to match
this new name too.
Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
---
...ptional_path.svg => virtio_user_as_exception_path.svg} | 0
doc/guides/howto/index.rst | 2 +-
...ptional_path.rst => virtio_user_as_exception_path.rst} | 8 ++++----
3 files changed, 5 insertions(+), 5 deletions(-)
rename doc/guides/howto/img/{virtio_user_as_exceptional_path.svg => virtio_user_as_exception_path.svg} (100%)
rename doc/guides/howto/{virtio_user_as_exceptional_path.rst => virtio_user_as_exception_path.rst} (96%)
diff --git a/doc/guides/howto/img/virtio_user_as_exceptional_path.svg b/doc/guides/howto/img/virtio_user_as_exception_path.svg
similarity index 100%
rename from doc/guides/howto/img/virtio_user_as_exceptional_path.svg
rename to doc/guides/howto/img/virtio_user_as_exception_path.svg
diff --git a/doc/guides/howto/index.rst b/doc/guides/howto/index.rst
index c2a2c60ddb..bf6337d021 100644
--- a/doc/guides/howto/index.rst
+++ b/doc/guides/howto/index.rst
@@ -15,7 +15,7 @@ HowTo Guides
pvp_reference_benchmark
vfd
virtio_user_for_container_networking
- virtio_user_as_exceptional_path
+ virtio_user_as_exception_path
packet_capture_framework
telemetry
debug_troubleshoot
diff --git a/doc/guides/howto/virtio_user_as_exceptional_path.rst b/doc/guides/howto/virtio_user_as_exception_path.rst
similarity index 96%
rename from doc/guides/howto/virtio_user_as_exceptional_path.rst
rename to doc/guides/howto/virtio_user_as_exception_path.rst
index 3d3d1b1219..a7f0d366fe 100644
--- a/doc/guides/howto/virtio_user_as_exceptional_path.rst
+++ b/doc/guides/howto/virtio_user_as_exception_path.rst
@@ -1,7 +1,7 @@
.. SPDX-License-Identifier: BSD-3-Clause
Copyright(c) 2016 Intel Corporation.
-.. _virtio_user_as_exceptional_path:
+.. _virtio_user_as_exception_path:
Virtio_user as Exception Path
=============================
@@ -39,11 +39,11 @@ This solution has a number of advantages over alternatives such as KNI:
on the polling DPDK threads.
The overview of an application using virtio-user as exception path is shown
-in :numref:`figure_virtio_user_as_exceptional_path`.
+in :numref:`figure_virtio_user_as_exception_path`.
-.. _figure_virtio_user_as_exceptional_path:
+.. _figure_virtio_user_as_exception_path:
-.. figure:: img/virtio_user_as_exceptional_path.*
+.. figure:: img/virtio_user_as_exception_path.*
Overview of a DPDK app using virtio-user as exception path
--
2.34.1