mirror of
https://gitlab.com/libvirt/libvirt.git
synced 2025-01-03 03:25:20 +00:00
tests: fix misc spelling errors reported by codespell
Reviewed-by: Peter Krempa <pkrempa@redhat.com> Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
This commit is contained in:
parent
f7a1805a7d
commit
9c1dc67403
@ -58,7 +58,7 @@ const char *fakedevicedir1 = FAKEDEVDIR1;
|
||||
* use /sys/fs/cgroup, because we want to make it easy to
|
||||
* detect places where we've not mocked enough syscalls.
|
||||
*
|
||||
* In any open/acces/mkdir calls we look at path and if
|
||||
* In any open/access/mkdir calls we look at path and if
|
||||
* it starts with /not/really/sys/fs/cgroup, we rewrite
|
||||
* the path to point at a subdirectory of the temporary
|
||||
* directory referred to by LIBVIRT_FAKE_ROOT_DIR env
|
||||
|
@ -34,7 +34,7 @@
|
||||
* too.
|
||||
*
|
||||
* On 64-bit hosts the stat & stat64 functions are identical, always
|
||||
* refering to the 64-bit ABI.
|
||||
* referring to the 64-bit ABI.
|
||||
*
|
||||
* On 32-bit hosts they refer to the 32-bit & 64-bit ABIs respectively.
|
||||
*
|
||||
@ -49,7 +49,7 @@
|
||||
* In GLibC there may be two additional functions exposed by the headers,
|
||||
* __xstat() and __xstat64(). When these exist, stat() and stat64() are
|
||||
* transparently rewritten to call __xstat() and __xstat64() respectively.
|
||||
* The former symbols will not actally exist in the library at all, only
|
||||
* The former symbols will not actually exist in the library at all, only
|
||||
* the header. The leading "__" indicates the symbols are a private impl
|
||||
* detail of the C library that applications should not care about.
|
||||
* Unfortunately, because we are trying to mock replace the C library,
|
||||
|
@ -2,7 +2,7 @@
|
||||
===========================
|
||||
|
||||
The various input-data-*.json files are a record of all the historical
|
||||
formats that libvirt has been able to produce data for. Everytime a
|
||||
formats that libvirt has been able to produce data for. Every time a
|
||||
new field is added to the JSON output, a *new* input data file should
|
||||
be created. We must not add new fields to existing input-data files,
|
||||
nor must we ever re-structure them if code changes, as we must check
|
||||
|
@ -1078,7 +1078,7 @@ open(const char *path, int flags, ...)
|
||||
|
||||
# ifdef __GLIBC__
|
||||
/* in some cases this function may not be present in headers, so we need
|
||||
* a declaration to silence the complier */
|
||||
* a declaration to silence the compiler */
|
||||
int
|
||||
__open_2(const char *path, int flags);
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user