Searched full:sake (Results 1 – 25 of 26) sorted by relevance
12
| /Documentation/filesystems/ext4/ |
| D | about.rst | 31 logical blocks, not raw LBAs, and not 1024-byte blocks. For the sake of
|
| /Documentation/devicetree/bindings/memory-controllers/fsl/ |
| D | imx8m-ddrc.yaml | 21 for the sake of "describing hardware"), it mostly just exposes firmware
|
| /Documentation/devicetree/bindings/display/panel/ |
| D | sharp,lq101r1sx01.yaml | 25 but for the sake of consistency this binding assumes that the same assignment
|
| /Documentation/devicetree/bindings/ |
| D | writing-bindings.rst | 30 - DON'T create nodes just for the sake of instantiating drivers. Multi-function
|
| /Documentation/firmware-guide/acpi/ |
| D | DSD-properties-rules.rst | 92 sake of code re-use, it may make sense to provide as much of the configuration
|
| /Documentation/crypto/ |
| D | api-samples.rst | 7 This code encrypts some data with AES-256-XTS. For sake of example,
|
| /Documentation/arch/arm/ |
| D | kernel_user_helpers.rst | 30 don't make binaries unable to run on earlier processors just for the sake
|
| /Documentation/input/ |
| D | uinput.rst | 42 the sake of simplicity.
|
| /Documentation/accounting/ |
| D | taskstats.rst | 90 set over time. However, for the sake of efficiency, an explicit deregistration
|
| /Documentation/driver-api/ |
| D | xillybus.rst | 253 This mechanism is used on non-PCIe buses as well for the sake of uniformity.
269 for each channel. For the sake of illustration, let's take the FPGA to host
|
| /Documentation/devicetree/bindings/mailbox/ |
| D | arm,mhuv3.yaml | 127 For the sake of simplicity maxItems is anyway capped to a most plausible
|
| /Documentation/admin-guide/mm/ |
| D | concepts.rst | 218 The `OOM killer` selects a task to sacrifice for the sake of the overall
|
| /Documentation/gpu/amdgpu/display/ |
| D | mpo-overview.rst | 196 For simplicity's sake, for discussing the hardware limitation, this
|
| /Documentation/driver-api/usb/ |
| D | writing_musb_glue_layer.rst | 120 For the sake of readability each function will be split in logical
581 for the sake of insight even though these might not be found in the
|
| /Documentation/usb/ |
| D | usbmon.rst | 149 have leading zeros, for the sake of human readers.
|
| /Documentation/filesystems/ |
| D | autofs-mount-control.rst | 103 sake of the problem explanation. The one important detail is that these
|
| /Documentation/dev-tools/ |
| D | coccinelle.rst | 353 developers. For sake of clarity, they should be organized in the
|
| /Documentation/scheduler/ |
| D | sched-capacity.rst | 50 the term ``capacity`` interchangeably with ``original capacity`` for the sake of
|
| /Documentation/process/ |
| D | 4.Coding.rst | 54 their own sake.
|
| /Documentation/admin-guide/blockdev/ |
| D | zram.rst | 38 For the sake of simplicity we skip error checking parts in most of the
|
| /Documentation/admin-guide/ |
| D | ext4.rst | 587 sake of simplicity.
|
| /Documentation/input/devices/ |
| D | elantech.rst | 86 completeness sake.
|
| /Documentation/mm/ |
| D | unevictable-lru.rst | 192 for the sake of expediency, to leave an unevictable folio on one of the regular
|
| /Documentation/userspace-api/ |
| D | landlock.rst | 550 escalations through renaming or linking, and for the sake of simplicity,
|
| /Documentation/devicetree/bindings/cpu/ |
| D | idle-states.yaml | 185 For sake of simplicity, let's consider a system with two idle states IDLE1,
|
12