Searched full:considered (Results 1 – 25 of 1082) sorted by relevance
12345678910>>...44
| /Linux-v5.15/Documentation/maintainer/ |
| D | maintainer-entry-profile.rst | 41 for a patch to be considered healthy enough for maintainer attention.
48 will be considered.
55 considered for the next -rc1. The reality is that most patches need to
58 week) that patches might be considered for merging and when patches need to
66 why they should be considered on an expedited schedule. A general
80 overview section, should be considered ready for new submissions.
|
| /Linux-v5.15/Documentation/ABI/testing/ |
| D | sysfs-bus-iio-proximity | 8 considered close to the device. If the value read from the
10 should typically be considered near.
|
| D | sysfs-devices-platform-soc-ipa | 66 perspective of the AP; this endpoint is considered an "IPA
77 perspective of the AP; this endpoint is considered an "IPA
|
| /Linux-v5.15/Documentation/admin-guide/hw-vuln/ |
| D | core-scheduling.rst | 101 The idle task is considered special, as it trusts everything and everything
114 then the sibling is considered to be in a `forced idle` state. I.e., it may
131 considered depending on whether a VM or a regular usermode process was running
152 When a system with core scheduling boots, all tasks are considered to trust
156 and are considered system-wide trusted. The forced-idling of siblings running
160 within such groups are considered to trust each other, but do not trust those
|
| /Linux-v5.15/Documentation/process/ |
| D | code-of-conduct-interpretation.rst | 52 considered a violation report unless you want it to be. If you are
93 sent to those mailing lists are considered covered by the Code of
111 may be considered for extreme circumstances.
119 standards or specifications, are not considered bugs.
|
| /Linux-v5.15/Documentation/devicetree/bindings/iio/ |
| D | common.yaml | 26 For proximity sensors whether an object can be considered near to the
32 considered 'near' to the device (an object is near to the
|
| /Linux-v5.15/tools/testing/ktest/examples/include/ |
| D | bisect.conf | 21 # You must set the commit that was considered good (git bisect good)
23 # You must set the commit that was considered bad (git bisect bad)
86 # Set the config that is considered bad.
|
| /Linux-v5.15/Documentation/xtensa/ |
| 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.
|
| /Linux-v5.15/Documentation/power/ |
| D | power_supply_class.rst | 106 Maximal/minimal means values of voltages when battery considered
125 design charge values, when battery considered full/empty.
133 considered full/empty at given conditions (temperature, age)".
210 seconds left for battery to be considered empty
213 seconds left for battery to be considered full
|
| /Linux-v5.15/Documentation/dev-tools/ |
| D | kmemleak.rst | 90 An allocated block of memory is considered orphan if no pointer to its
94 block to a freeing function and therefore the block is considered a
100 considered orphan)
108 4. the remaining white objects are considered orphan and reported via
115 block is not considered a leak. One example is __vmalloc().
|
| /Linux-v5.15/Documentation/devicetree/bindings/display/panel/ |
| D | sharp,ls037v7dw01.yaml | 12 configured with external pulls, all the GPIOs are considered optional with holes
39 with external pulls, all the GPIOs are considered
|
| /Linux-v5.15/tools/perf/arch/powerpc/annotate/ |
| D | instructions.c | 32 * those are considered 'calls' since they update LR. in powerpc__associate_instruction_ops()
43 * instructions ending with 'lr' are considered to be in powerpc__associate_instruction_ops()
|
| /Linux-v5.15/Documentation/mhi/ |
| 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-v5.15/arch/mips/include/asm/mach-generic/ |
| D | spaces.h | 46 * Memory above this physical address will be considered highmem.
73 * Memory above this physical address will be considered highmem.
|
| /Linux-v5.15/arch/arm/kernel/ |
| D | devtree.c | 70 * considered invalid logical map entries since the logical map must in arm_dt_init_cpu_maps()
94 * properties is considered invalid to build the in arm_dt_init_cpu_maps()
176 * a reg property, the DT CPU list can be considered valid and the in arm_dt_init_cpu_maps()
|
| /Linux-v5.15/include/uapi/linux/ |
| D | falloc.h | 26 * considered an illegal operation - just use ftruncate(2) if you need
57 * the file is considered an illegal operation - just use ftruncate(2) or
|
| /Linux-v5.15/Documentation/devicetree/bindings/net/ |
| D | fsl-tsec-phy.txt | 22 When device_type is "mdio", the following strings are also considered:
43 is considered instructive, rather than descriptive. The reg property should
|
| /Linux-v5.15/Documentation/admin-guide/device-mapper/ |
| 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-v5.15/Documentation/devicetree/bindings/input/ |
| D | adc-keys.txt | 9 considered up.
22 considered pressed.
|
| /Linux-v5.15/certs/ |
| D | Kconfig | 50 the keyring are considered to be trusted. Keys may be added at will
99 Keys in the keyring are considered entirely untrusted. Keys in this
|
| /Linux-v5.15/Documentation/devicetree/bindings/cpu/ |
| D | cpu-topology.txt | 36 with bindings standardized in [4] is therefore considered invalid.
65 Any other configuration is considered invalid.
116 Any other configuration is considered invalid.
133 Any other configuration is considered invalid.
159 Any other configuration is considered invalid.
|
| /Linux-v5.15/include/trace/events/ |
| D | compaction.h | 254 __field(unsigned int, considered)
263 __entry->considered = zone->compact_considered;
273 __entry->considered,
|
| /Linux-v5.15/net/ipv6/ |
| D | exthdrs_core.c | 61 * are considered as unparsable.
65 * - ESP is unparsable for now and considered like
173 * NEXTHDR_NONE it is considered invalid.
|
| /Linux-v5.15/include/linux/ |
| D | freezer.h | 101 * considered frozen enough by freezers.
116 * considered again and tries to freeze if freezing condition is already in
146 * state is reached. IOW, if this function returns %true, @p is considered
|
| /Linux-v5.15/Documentation/block/ |
| D | pr.rst | 44 All initiators with a registered key are considered reservation
51 All initiators with a registered key are considered reservation
|
12345678910>>...44
