mirrors/pipewire
1
0
Fork 0
mirror of https://gitlab.freedesktop.org/pipewire/pipewire.git synced 2026-04-01 07:15:39 -04:00
Code Issues Projects Releases Packages Wiki Activity Actions

Fix typos

Browse source 
found them with codespell.

Signed-off-by: Diego Viola <diego.viola@gmail.com>
This commit is contained in:
Diego Viola 2024-05-20 10:45:04 -03:00 • committed by Wim Taymans
parent 8a24ad3073
commit 7410755c03
45 changed files with 100 additions and 100 deletions
Download patch file Download diff file Expand all files Collapse all files

2
doc/dox/internals/daemon.dox
View file

@ -139,7 +139,7 @@ more debugging. This variable supports the following format:
shell globs to match on log topics and the levels are the respective
log level to set for that topic. Globs are applied in order and a matching
glob overrides an earlier glob for that category. A level without a glob
prefix will set the global log level and is a more preformant version of
prefix will set the global log level and is a more performant version of
`*:<level>`. For example, `PIPEWIRE_DEBUG=E,mod.*:D,mod.foo:X` enables global error messages,
debugging on all modules but no messages on the foo module.
- `<level>` specifies the log level:

2
doc/dox/internals/library.dox
View file

@ -56,7 +56,7 @@ for state changes.
# Versioning
All interfaces have a version number. The maximum supported version
number of an interface is advertized in the registry global event.
number of an interface is advertised in the registry global event.
A client asks for a specific version of an interface when it binds
to them. It is the task of the server to adapt to the version of the

12
doc/dox/internals/protocol.dox
View file

@ -157,7 +157,7 @@ The id and seq should be copied from the Ping event.
### Core::Error (Opcode 4)
An error occured in an object on the client.
An error occurred in an object on the client.
```
Struct(
@ -274,11 +274,11 @@ Destroy an object.
## Core Events
Core events are emited by the server.
Core events are emitted by the server.
### Core::Info (Opcode 0)
Emited by the server upon connection with the more information about the
Emitted by the server upon connection with the more information about the
server.
```
@ -309,7 +309,7 @@ server.
### Core::Done (Opcode 1)
Emited as a result of a client Sync method.
Emitted as a result of a client Sync method.
```
Struct(
@ -322,7 +322,7 @@ id and seq are passed from the client Sync request.
### Core::Ping (Opcode 2)
Emited by the server when it wants to check if a client is alive or ensure
Emitted by the server when it wants to check if a client is alive or ensure
that it has processed the previous events.
```
@ -1236,7 +1236,7 @@ about the the newly allocated buffer memory.
- type: the plane memory type
- memfd: the plane memfd
- mapoffset: the start offset of where the buffer memory starts
- maxsize: the maxiumum size of the memory.
- maxsize: the maximum size of the memory.
## ClientNode events

2
doc/dox/internals/scheduling.dox
View file

@ -188,7 +188,7 @@ The driver calculates some stats about cpu time etc.
# Remote nodes.
For remote nodes, the eventfd and the activation is transfered from the server
For remote nodes, the eventfd and the activation is transferred from the server
to the client.
This means that writing to the remote client eventfd will wake the client directly