From nobody Sun Feb 8 22:57:45 2026 Delivered-To: importer@patchew.org Received-SPF: pass (zohomail.com: domain of redhat.com designates 170.10.129.124 as permitted sender) client-ip=170.10.129.124; envelope-from=libvir-list-bounces@redhat.com; helo=us-smtp-delivery-124.mimecast.com; Authentication-Results: mx.zohomail.com; dkim=pass; spf=pass (zohomail.com: domain of redhat.com designates 170.10.129.124 as permitted sender) smtp.mailfrom=libvir-list-bounces@redhat.com; dmarc=pass(p=none dis=none) header.from=redhat.com ARC-Seal: i=1; a=rsa-sha256; t=1649865843; cv=none; d=zohomail.com; s=zohoarc; b=NF9Ng1t6SRlUhn++6mEBS4PVoMQxn1Q5yj+GOo5vZYsyTpZirDHah6T5sgbOhE4FIU86myZKjMz06DL+C1yNMEnSE2IPJXVXTpnAflndj596G44EtktFAXu7PmRkEpJsDh3Yd1mKqwjz+O1kioaMtt3vL03N7puEWeWdJTF9CU0= ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=zohomail.com; s=zohoarc; t=1649865843; h=Content-Type:Content-Transfer-Encoding:Date:From:In-Reply-To:List-Subscribe:List-Post:List-Id:List-Archive:List-Help:List-Unsubscribe:MIME-Version:Message-ID:References:Sender:Subject:To; bh=EUKXUnyZAa0zQOQhTEjsYcpgJSmucbNsktQyuCq7WQg=; b=YJqOnXFt6kM714WiU9Ie2BcF/vvZmxxIy9+7rwmsnrLGFQpGRX41I0auP3iU2V0EAdsgI6+aEj2vb92rkzmCnsMUv5Aw48PgNu1Rt6CSYS61h+2ixezNTLown10bOGFzZ05kwff9NERMgiXnYgx4Iq3703eMDipiSo/Kz/ChSO8= ARC-Authentication-Results: i=1; mx.zohomail.com; dkim=pass; spf=pass (zohomail.com: domain of redhat.com designates 170.10.129.124 as permitted sender) smtp.mailfrom=libvir-list-bounces@redhat.com; dmarc=pass header.from= (p=none dis=none) Return-Path: Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by mx.zohomail.com with SMTPS id 1649865843198466.34537250906317; Wed, 13 Apr 2022 09:04:03 -0700 (PDT) Received: from mimecast-mx02.redhat.com (mimecast-mx02.redhat.com [66.187.233.88]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-209-uVJaCh4cNqK8723sLytgqQ-1; Wed, 13 Apr 2022 12:03:11 -0400 Received: from smtp.corp.redhat.com (int-mx08.intmail.prod.int.rdu2.redhat.com [10.11.54.8]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id AF0B118E52A6; Wed, 13 Apr 2022 16:02:25 +0000 (UTC) Received: from mm-prod-listman-01.mail-001.prod.us-east-1.aws.redhat.com (mm-prod-listman-01.mail-001.prod.us-east-1.aws.redhat.com [10.30.29.100]) by smtp.corp.redhat.com (Postfix) with ESMTP id 9B004C27E92; Wed, 13 Apr 2022 16:02:25 +0000 (UTC) Received: from mm-prod-listman-01.mail-001.prod.us-east-1.aws.redhat.com (localhost [IPv6:::1]) by mm-prod-listman-01.mail-001.prod.us-east-1.aws.redhat.com (Postfix) with ESMTP id 203C41940345; Wed, 13 Apr 2022 16:02:24 +0000 (UTC) Received: from smtp.corp.redhat.com (int-mx07.intmail.prod.int.rdu2.redhat.com [10.11.54.7]) by mm-prod-listman-01.mail-001.prod.us-east-1.aws.redhat.com (Postfix) with ESMTP id CF9FB194E015 for ; Wed, 13 Apr 2022 16:02:22 +0000 (UTC) Received: by smtp.corp.redhat.com (Postfix) id C487A145BA60; Wed, 13 Apr 2022 16:02:22 +0000 (UTC) Received: from speedmetal.lan (unknown [10.40.208.35]) by smtp.corp.redhat.com (Postfix) with ESMTP id 3D4C9145BA5B for ; Wed, 13 Apr 2022 16:02:22 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1649865842; h=from:from:sender:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references:list-id:list-help: list-unsubscribe:list-subscribe:list-post; bh=EUKXUnyZAa0zQOQhTEjsYcpgJSmucbNsktQyuCq7WQg=; b=LHSFRiytTelXTU1TGBueL7JDwZio7wxGviKohrnkyTtFZYddNWWHqXcig0UlPii88uMqlJ mAMxN7kAnfuTeB8EtIv0/tYebsvc9TbKc4kpLA8ga78uUigutykEjAdQb8w5uwhoPRnCLu ZjKx3fjzlvDyzC6UnLghVHu3eAUBOQE= X-MC-Unique: uVJaCh4cNqK8723sLytgqQ-1 X-Original-To: libvir-list@listman.corp.redhat.com From: Peter Krempa To: libvir-list@redhat.com Subject: [PATCH 06/14] docs: drvnodedev: Fix local anchor links Date: Wed, 13 Apr 2022 18:02:07 +0200 Message-Id: In-Reply-To: References: MIME-Version: 1.0 X-Scanned-By: MIMEDefang 2.85 on 10.11.54.7 X-BeenThere: libvir-list@redhat.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Development discussions about the libvirt library & tools List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: libvir-list-bounces@redhat.com Sender: "libvir-list" X-Scanned-By: MIMEDefang 2.85 on 10.11.54.8 Authentication-Results: relay.mimecast.com; auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=libvir-list-bounces@redhat.com X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Transfer-Encoding: quoted-printable X-ZohoMail-DKIM: pass (identity @redhat.com) X-ZM-MESSAGEID: 1649865843883100001 Content-Type: text/plain; charset="utf-8"; x-default="true" Original conversion didn't properly convert local links. Fix them by pointing to the section name. In certain cases this requires reformulation of the text. Signed-off-by: Peter Krempa --- docs/drvnodedev.rst | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/docs/drvnodedev.rst b/docs/drvnodedev.rst index cddb36c73b..d333a9dca6 100644 --- a/docs/drvnodedev.rst +++ b/docs/drvnodedev.rst @@ -59,8 +59,7 @@ PCI host devices ``capability`` When used as top level element, the supported values for the ``type`` - attribute are ``pci`` and ``phys_function`` (see `SR-IOV - below <#SRIOVCap>`__). + attribute are ``pci`` and ``phys_function`` (see `SR-IOV capability`_ b= elow). :: @@ -103,9 +102,10 @@ multiple devices called virtual functions (VFs) sharin= g their configuration with the underlying PF. Despite the SR-IOV specification, the amount of VFs tha= t can be created on a PF varies among manufacturers. -Suppose the NIC `above <#PCI>`__ was also SR-IOV capable, it would also in= clude -a nested ```` element enumerating all virtual functions availa= ble on -the physical device (physical port) like in the example below. +Suppose the NIC above in `PCI host devices`_ was also SR-IOV capable, it w= ould +also include a nested ```` element enumerating all virtual +functions available on the physical device (physical port) like in the exa= mple +below. :: @@ -146,8 +146,8 @@ of the XML format for the ``mdev_types`` capability can= be found `here `__. The following example shows how we might represent an NVIDIA GPU device th= at -supports mediated devices. See below for `more information about mediated -devices <#MDEV>`__. +supports mediated devices. See below for more info on +`Mediated devices (MDEVs)`_. :: @@ -281,7 +281,7 @@ covers the following features: Because mediated devices are instantiated from vendor specific templates, = simply called 'types', information describing these types is contained within the -parent device's capabilities (see the example in `PCI host devices <#PCI>`= __). +parent device's capabilities (see the example in `PCI host devices`_). To list all devices capable of creating mediated devices, the following co= mmand can be used. --=20 2.35.1