mirror of
https://github.com/LadybirdBrowser/ladybird.git
synced 2024-12-26 12:41:59 +03:00
Documentation: Correct some typos found in kernel markdown files
This commit is contained in:
parent
8eaf28b4ce
commit
cbdb5f926c
Notes:
sideshowbarker
2024-07-17 03:03:44 +09:00
Author: https://github.com/afsong 🔰 Commit: https://github.com/SerenityOS/serenity/commit/cbdb5f926c Pull-request: https://github.com/SerenityOS/serenity/pull/18652 Reviewed-by: https://github.com/AtkinsSJ ✅
@ -32,7 +32,7 @@ so the userland program could know about the situation and act accordingly.
|
||||
|
||||
An exception to this is when there's simply no way to propagate the error code to the userland program.
|
||||
Maybe it's a `ATAPort` (in the IDE ATA code) that asynchronously tries to handle reading data from the harddrive,
|
||||
but because of the async operation, we can't send the `errno` code back to userland, so we what we do is
|
||||
but because of the async operation, we can't send the `errno` code back to userland, so what we do is
|
||||
to ensure that internal functions still use the `ErrorOr<>` return type, and in main calling function, we use
|
||||
other meaningful infrastructure utilities in the Kernel to indicate that the operation failed.
|
||||
|
||||
|
@ -19,7 +19,7 @@ from the framebuffer.
|
||||
# DisplayConnector Devices
|
||||
|
||||
The Display Connector devices are an abstraction layer to what is essentially the
|
||||
management layer of hardware display (commonly known as scanouts too) output connectors.
|
||||
management layer of hardware display (commonly known as scanouts) output connectors.
|
||||
The idea of using such type of device was inspired by Linux, which has a struct called
|
||||
`drm_connector` as a base structure for other derived structures in the various Linux DRM drivers.
|
||||
|
||||
|
@ -7,7 +7,7 @@ each `InodeIndex` actually represent a known object, so it is guaranteed to be
|
||||
the same always for global ProcFS objects. For process ID directories, once that
|
||||
process has been killed, its primary segment value is no longer valid and hence
|
||||
all sub-segments of it are not relevant anymore, but if the process is still alive,
|
||||
it is guaranteed that accessing the same `InodeIndex` in regard to a object tied to
|
||||
it is guaranteed that accessing the same `InodeIndex` in regard to an object tied to
|
||||
a process directory will provide the expected object.
|
||||
|
||||
## The goal - zero allocations when creating new process
|
||||
|
@ -20,7 +20,7 @@ with very small overhead until actual IO is performed.
|
||||
Currently, the `/tmp` directory is the **place** for facilitating the inter-process
|
||||
communication layer, with many Unix sockets nodes being present in the directory.
|
||||
|
||||
Many test suites in the project leverage the `/tmp` for placing their test files
|
||||
Many test suites in the project leverage `/tmp` for placing their test files
|
||||
when trying to check the correctness of many system-related functionality.
|
||||
Other programs rely on `/tmp` for placing their temporary files to properly function.
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user