| /linux/Documentation/ABI/testing/ |
| H A D | sysfs-bus-iio-proximity | 8 considered close to the device. If the value read from the
10 should typically be considered near.
|
| /linux/Documentation/arch/xtensa/ |
| H A D | booting.rst | 20 virtual mapping. It is considered physical if it is within the range of
22 XCHAL_KSEG_PADDR + XCHAL_KSEG_SIZE), otherwise it is considered virtual.
|
| H A D | mmu.rst | 54 1. Only top level simple-bus nodes are considered
56 2. Only one (first) simple-bus node is considered
60 4. Only the first triplet in the "ranges" property is considered
|
| /linux/Documentation/process/ |
| H A D | contribution-maturity-model.rst | 58 * A Software Engineer’s upstream code contributions will be considered
69 ACM, etc.), are considered part of an engineer’s work.
70 * A Software Engineer’s community contributions will be considered in
104 * Upstream kernel development is considered a formal job position, with
|
| /linux/include/trace/events/ |
| H A D | compaction.h | 249 __field(unsigned int, considered)
258 __entry->considered = zone->compact_considered;
268 __entry->considered,
|
| /linux/Documentation/admin-guide/device-mapper/ |
| H A D | dm-log.rst | 9 mirrors, a region would be considered dirty/inconsistent while you
12 Once all writes are complete, the region is considered clean again.
|
| /linux/Documentation/translations/zh_TW/process/ |
| H A D | index.rst | 59 volatile-considered-harmful
|
| H A D | volatile-considered-harmful.rst | 7 :Original: :ref:`Documentation/process/volatile-considered-harmful.rst
|
| /linux/Documentation/admin-guide/hw-vuln/ |
| H A D | core-scheduling.rst | 102 The idle task is considered special, as it trusts everything and everything
115 then the sibling is considered to be in a `forced idle` state. I.e., it may
132 considered depending on whether a VM or a regular usermode process was running
153 When a system with core scheduling boots, all tasks are considered to trust
157 and are considered system-wide trusted. The forced-idling of siblings running
161 within such groups are considered to trust each other, but do not trust those
|
| /linux/Documentation/networking/ |
| H A D | sriov.rst | 19 the API is considered frozen; no new functionality or extensions
|
| /linux/Documentation/translations/zh_CN/process/ |
| H A D | index.rst | 85 volatile-considered-harmful
|
| H A D | volatile-considered-harmful.rst | 5 :Original: :ref:`Documentation/process/volatile-considered-harmful.rst
|
| /linux/Documentation/mhi/ |
| H A D | mhi.rst | 106 * Ring is considered empty when RP == WP.
107 * Ring is considered full when WP + 1 == RP.
134 * Ring is considered empty (no events to service) when WP + 1 == RP.
135 * Ring is considered full of events when RP == WP.
|
| /linux/Documentation/block/ |
| H A D | pr.rst | 44 All initiators with a registered key are considered reservation
51 All initiators with a registered key are considered reservation
|
| /linux/Documentation/arch/arm64/ |
| H A D | kdump.rst | 22 be considered if the crashkernel is reserved from the high memory area.
38 above, the rest of system RAM is considered high memory.
|
| /linux/scripts/coccinelle/misc/ |
| H A D | ifcol.cocci | 9 //# is not visually aligned may be considered to be in the same column.
|
| /linux/LICENSES/exceptions/ |
| H A D | Linux-syscall-note | 14 services by normal system calls - this is merely considered normal use
|
| /linux/Documentation/driver-api/ |
| H A D | s390-drivers.rst | 26 not strictly considered I/O devices. They are considered here as well,
|
| /linux/Documentation/arch/arm/ |
| H A D | microchip.rst | 85 * Datasheet (can be considered as covering the whole family)
212 considered as "Unstable". To be completely clear, any at91 binding can change at
|
| /linux/Documentation/doc-guide/ |
| H A D | checktransupdate.rst | 15 from HEAD. If any differences occur, the file is considered as out-of-date,
|
| /linux/Documentation/userspace-api/media/v4l/ |
| H A D | io.rst | 22 Video overlay can be considered another I/O method, although the
|
| H A D | video.rst | 12 Video, S-Video and RGB connectors. Camera sensors are also considered to
|
| /linux/Documentation/ABI/stable/ |
| H A D | vdso | 31 ABI of those symbols is considered stable. It may vary across architectures,
|
| H A D | sysfs-module | 23 considered stable, only the fact that they will be
|
| /linux/Documentation/virt/kvm/devices/ |
| H A D | mpic.rst | 37 For edge-triggered interrupts: Writing 1 is considered an activating
|