qemu-trivial
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH] docs: Replace Qemu -> QEMU


From: Laurent Vivier
Subject: Re: [PATCH] docs: Replace Qemu -> QEMU
Date: Tue, 26 Apr 2022 12:39:21 +0200
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.8.0

Le 22/04/2022 à 10:30, Stefan Weil a écrit :
Signed-off-by: Stefan Weil <sw@weilnetz.de>
---
  docs/pcie_sriov.txt | 6 +++---
  1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/docs/pcie_sriov.txt b/docs/pcie_sriov.txt
index f5e891e1d4..11158dbf88 100644
--- a/docs/pcie_sriov.txt
+++ b/docs/pcie_sriov.txt
@@ -8,8 +8,8 @@ of a PCI Express device. It allows a single physical function 
(PF) to appear as
  virtual functions (VFs) for the main purpose of eliminating software
  overhead in I/O from virtual machines.
-Qemu now implements the basic common functionality to enable an emulated device
-to support SR/IOV. Yet no fully implemented devices exists in Qemu, but a
+QEMU now implements the basic common functionality to enable an emulated device
+to support SR/IOV. Yet no fully implemented devices exists in QEMU, but a
  proof-of-concept hack of the Intel igb can be found here:
git://github.com/knuto/qemu.git sriov_patches_v5
@@ -18,7 +18,7 @@ Implementation
  ==============
  Implementing emulation of an SR/IOV capable device typically consists of
  implementing support for two types of device classes; the "normal" physical 
device
-(PF) and the virtual device (VF). From Qemu's perspective, the VFs are just
+(PF) and the virtual device (VF). From QEMU's perspective, the VFs are just
  like other devices, except that some of their properties are derived from
  the PF.


Applied to my trivial-patches branch.

Thanks,
Laurent



reply via email to

[Prev in Thread] Current Thread [Next in Thread]