提交 0546b8c2 编写于 作者: S Stefan Weil 提交者: Stefan Hajnoczi

Spelling fixes in comments and documentation

These wrong spellings were detected by codespell:

* successully -> successfully

* alot -> a lot

* wanna -> want to

* infomation -> information

* occured -> occurred

["also is" -> "is also" and "ressources" -> "resources" suggested by
Peter Maydell <peter.maydell@linaro.org>]
Signed-off-by: NStefan Weil <sw@weilnetz.de>
Signed-off-by: NStefan Hajnoczi <stefanha@linux.vnet.ibm.com>
上级 93d3ad2a
...@@ -31,7 +31,7 @@ Arguments: ...@@ -31,7 +31,7 @@ Arguments:
Returns: Returns:
H_SUCCESS : Successully called the RTAS function (RTAS result H_SUCCESS : Successfully called the RTAS function (RTAS result
will have been stored in the parameter block) will have been stored in the parameter block)
H_PARAMETER : Unknown token H_PARAMETER : Unknown token
......
...@@ -58,11 +58,11 @@ try ... ...@@ -58,11 +58,11 @@ try ...
xhci controller support xhci controller support
----------------------- -----------------------
There also is xhci host controller support available. It got alot There is also xhci host controller support available. It got a lot
less testing than ehci and there are a bunch of known limitations, so less testing than ehci and there are a bunch of known limitations, so
ehci may work better for you. On the other hand the xhci hardware ehci may work better for you. On the other hand the xhci hardware
design is much more virtualization-friendly, thus xhci emulation uses design is much more virtualization-friendly, thus xhci emulation uses
less ressources (especially cpu). If you wanna give xhci a try less resources (especially cpu). If you want to give xhci a try
use this to add the host controller ... use this to add the host controller ...
qemu -device nec-usb-xhci,id=xhci qemu -device nec-usb-xhci,id=xhci
......
...@@ -96,7 +96,7 @@ typedef struct XenPTRegion { ...@@ -96,7 +96,7 @@ typedef struct XenPTRegion {
* - do NOT use ALL F for init_val, otherwise the tbl will not be registered. * - do NOT use ALL F for init_val, otherwise the tbl will not be registered.
*/ */
/* emulated register infomation */ /* emulated register information */
struct XenPTRegInfo { struct XenPTRegInfo {
uint32_t offset; uint32_t offset;
uint32_t size; uint32_t size;
...@@ -140,7 +140,7 @@ typedef int (*xen_pt_reg_size_init_fn) ...@@ -140,7 +140,7 @@ typedef int (*xen_pt_reg_size_init_fn)
(XenPCIPassthroughState *, const XenPTRegGroupInfo *, (XenPCIPassthroughState *, const XenPTRegGroupInfo *,
uint32_t base_offset, uint8_t *size); uint32_t base_offset, uint8_t *size);
/* emulated register group infomation */ /* emulated register group information */
struct XenPTRegGroupInfo { struct XenPTRegGroupInfo {
uint8_t grp_id; uint8_t grp_id;
XenPTRegisterGroupType grp_type; XenPTRegisterGroupType grp_type;
......
...@@ -562,7 +562,7 @@ static int xen_pt_exp_rom_bar_reg_write(XenPCIPassthroughState *s, ...@@ -562,7 +562,7 @@ static int xen_pt_exp_rom_bar_reg_write(XenPCIPassthroughState *s,
return 0; return 0;
} }
/* Header Type0 reg static infomation table */ /* Header Type0 reg static information table */
static XenPTRegInfo xen_pt_emu_reg_header0[] = { static XenPTRegInfo xen_pt_emu_reg_header0[] = {
/* Vendor ID reg */ /* Vendor ID reg */
{ {
...@@ -753,7 +753,7 @@ static XenPTRegInfo xen_pt_emu_reg_header0[] = { ...@@ -753,7 +753,7 @@ static XenPTRegInfo xen_pt_emu_reg_header0[] = {
* Vital Product Data Capability * Vital Product Data Capability
*/ */
/* Vital Product Data Capability Structure reg static infomation table */ /* Vital Product Data Capability Structure reg static information table */
static XenPTRegInfo xen_pt_emu_reg_vpd[] = { static XenPTRegInfo xen_pt_emu_reg_vpd[] = {
{ {
.offset = PCI_CAP_LIST_NEXT, .offset = PCI_CAP_LIST_NEXT,
...@@ -775,7 +775,7 @@ static XenPTRegInfo xen_pt_emu_reg_vpd[] = { ...@@ -775,7 +775,7 @@ static XenPTRegInfo xen_pt_emu_reg_vpd[] = {
* Vendor Specific Capability * Vendor Specific Capability
*/ */
/* Vendor Specific Capability Structure reg static infomation table */ /* Vendor Specific Capability Structure reg static information table */
static XenPTRegInfo xen_pt_emu_reg_vendor[] = { static XenPTRegInfo xen_pt_emu_reg_vendor[] = {
{ {
.offset = PCI_CAP_LIST_NEXT, .offset = PCI_CAP_LIST_NEXT,
...@@ -866,7 +866,7 @@ static int xen_pt_linkctrl2_reg_init(XenPCIPassthroughState *s, ...@@ -866,7 +866,7 @@ static int xen_pt_linkctrl2_reg_init(XenPCIPassthroughState *s,
return 0; return 0;
} }
/* PCI Express Capability Structure reg static infomation table */ /* PCI Express Capability Structure reg static information table */
static XenPTRegInfo xen_pt_emu_reg_pcie[] = { static XenPTRegInfo xen_pt_emu_reg_pcie[] = {
/* Next Pointer reg */ /* Next Pointer reg */
{ {
...@@ -981,7 +981,7 @@ static int xen_pt_pmcsr_reg_write(XenPCIPassthroughState *s, ...@@ -981,7 +981,7 @@ static int xen_pt_pmcsr_reg_write(XenPCIPassthroughState *s,
return 0; return 0;
} }
/* Power Management Capability reg static infomation table */ /* Power Management Capability reg static information table */
static XenPTRegInfo xen_pt_emu_reg_pm[] = { static XenPTRegInfo xen_pt_emu_reg_pm[] = {
/* Next Pointer reg */ /* Next Pointer reg */
{ {
...@@ -1259,7 +1259,7 @@ static int xen_pt_msgdata_reg_write(XenPCIPassthroughState *s, ...@@ -1259,7 +1259,7 @@ static int xen_pt_msgdata_reg_write(XenPCIPassthroughState *s,
return 0; return 0;
} }
/* MSI Capability Structure reg static infomation table */ /* MSI Capability Structure reg static information table */
static XenPTRegInfo xen_pt_emu_reg_msi[] = { static XenPTRegInfo xen_pt_emu_reg_msi[] = {
/* Next Pointer reg */ /* Next Pointer reg */
{ {
...@@ -1396,7 +1396,7 @@ static int xen_pt_msixctrl_reg_write(XenPCIPassthroughState *s, ...@@ -1396,7 +1396,7 @@ static int xen_pt_msixctrl_reg_write(XenPCIPassthroughState *s,
return 0; return 0;
} }
/* MSI-X Capability Structure reg static infomation table */ /* MSI-X Capability Structure reg static information table */
static XenPTRegInfo xen_pt_emu_reg_msix[] = { static XenPTRegInfo xen_pt_emu_reg_msix[] = {
/* Next Pointer reg */ /* Next Pointer reg */
{ {
......
...@@ -89,7 +89,7 @@ static void help(void) ...@@ -89,7 +89,7 @@ static void help(void)
" '-r' tries to repair any inconsistencies that are found during the check.\n" " '-r' tries to repair any inconsistencies that are found during the check.\n"
" '-r leaks' repairs only cluster leaks, whereas '-r all' fixes all\n" " '-r leaks' repairs only cluster leaks, whereas '-r all' fixes all\n"
" kinds of errors, with a higher risk of choosing the wrong fix or\n" " kinds of errors, with a higher risk of choosing the wrong fix or\n"
" hiding corruption that has already occured.\n" " hiding corruption that has already occurred.\n"
"\n" "\n"
"Parameters to snapshot subcommand:\n" "Parameters to snapshot subcommand:\n"
" 'snapshot' is the name of the snapshot to create, apply or delete\n" " 'snapshot' is the name of the snapshot to create, apply or delete\n"
......
...@@ -87,7 +87,7 @@ Perform a consistency check on the disk image @var{filename}. ...@@ -87,7 +87,7 @@ Perform a consistency check on the disk image @var{filename}.
If @code{-r} is specified, qemu-img tries to repair any inconsistencies found If @code{-r} is specified, qemu-img tries to repair any inconsistencies found
during the check. @code{-r leaks} repairs only cluster leaks, whereas during the check. @code{-r leaks} repairs only cluster leaks, whereas
@code{-r all} fixes all kinds of errors, with a higher risk of choosing the @code{-r all} fixes all kinds of errors, with a higher risk of choosing the
wrong fix or hiding corruption that has already occured. wrong fix or hiding corruption that has already occurred.
Only the formats @code{qcow2}, @code{qed} and @code{vdi} support Only the formats @code{qcow2}, @code{qed} and @code{vdi} support
consistency checks. consistency checks.
......
Markdown is supported
0% .
You are about to add 0 people to the discussion. Proceed with caution.
先完成此消息的编辑!
想要评论请 注册