[ovs-dev] [PATCH] docs: fix a typo in vhost-user documentation.

Darrell Ball dball at vmware.com
Wed Sep 6 07:34:28 UTC 2017


I had applied the patch to dpdk_merge here

https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_darball_ovs_commits_dpdk-5Fmerge&d=DwIGaQ&c=uilaK90D4TOVoH58JNXRgQ&r=BVhFA09CGX7JQ5Ih-uZnsw&m=A2_FCacqbp2moAo3HGFlTuxsjONUGhlN42OBcAuQQ6w&s=b6btPKhgvOFr2GOUYvktND6kaC6jc3fXI-mXfvNgXOU&e=



On 9/5/17, 8:21 AM, "ovs-dev-bounces at openvswitch.org on behalf of Rami Rosen" <ovs-dev-bounces at openvswitch.org on behalf of rami.rosen at intel.com> wrote:

    This patch fixes a trivial typo in vhost-user documentation:
    the path to the second socket should be /tmp/dpdkvhostclient1
    and not /tmp/dpdkvhostclient0.
    
    Signed-off-by: Rami Rosen <rami.rosen at intel.com>
    ---
     Documentation/topics/dpdk/vhost-user.rst | 2 +-
     1 file changed, 1 insertion(+), 1 deletion(-)
    
    diff --git a/Documentation/topics/dpdk/vhost-user.rst b/Documentation/topics/dpdk/vhost-user.rst
    index a3d5de382..d2942034d 100644
    --- a/Documentation/topics/dpdk/vhost-user.rst
    +++ b/Documentation/topics/dpdk/vhost-user.rst
    @@ -44,7 +44,7 @@ existing bridge called ``br0``::
     
     For the above examples to work, an appropriate server socket must be created
     at the paths specified (``/tmp/dpdkvhostclient0`` and
    -``/tmp/dpdkvhostclient0``).  These sockets can be created with QEMU; see the
    +``/tmp/dpdkvhostclient1``).  These sockets can be created with QEMU; see the
     :ref:`vhost-user client <dpdk-vhost-user-client>` section for details.
     
     vhost-user vs. vhost-user-client
    -- 
    2.11.0
    
    _______________________________________________
    dev mailing list
    dev at openvswitch.org
    https://urldefense.proofpoint.com/v2/url?u=https-3A__mail.openvswitch.org_mailman_listinfo_ovs-2Ddev&d=DwICAg&c=uilaK90D4TOVoH58JNXRgQ&r=BVhFA09CGX7JQ5Ih-uZnsw&m=a4UJgvV1Bp7uBSplNVecu4qSwGzodfWOsb8MWVSQCRo&s=brxXzJJvCkVp9I6sBvMxEDxIYWOi7FuC9416zP-BAhQ&e= 
    



More information about the dev mailing list