Searched full:considered (Results 1 – 25 of 965) sorted by relevance
12345678910>>...39
| /Linux-v5.4/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.4/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.4/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.
|
| 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-v5.4/Documentation/dev-tools/ |
| D | kmemleak.rst | 91 An allocated block of memory is considered orphan if no pointer to its
95 block to a freeing function and therefore the block is considered a
101 considered orphan)
109 4. the remaining white objects are considered orphan and reported via
116 block is not considered a leak. One example is __vmalloc().
|
| /Linux-v5.4/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.4/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.4/certs/ |
| D | Kconfig | 24 the keyring are considered to be trusted. Keys may be added at will
73 Keys in the keyring are considered entirely untrusted. Keys in this
|
| /Linux-v5.4/arch/mips/include/asm/mach-generic/ |
| D | spaces.h | 50 * Memory above this physical address will be considered highmem.
77 * Memory above this physical address will be considered highmem.
|
| /Linux-v5.4/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.4/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
|
| D | blkzoned.h | 30 * Any other value not defined is reserved and must be considered as invalid.
63 * be considered invalid.
|
| /Linux-v5.4/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.4/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.4/include/trace/events/ |
| D | compaction.h | 254 __field(unsigned int, considered)
263 __entry->considered = zone->compact_considered;
273 __entry->considered,
|
| /Linux-v5.4/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.4/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.4/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.4/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
|
| /Linux-v5.4/fs/xfs/ |
| D | Kconfig | 82 This feature is considered EXPERIMENTAL. Use with caution!
100 This feature is considered EXPERIMENTAL. Use with caution!
|
| /Linux-v5.4/Documentation/filesystems/ |
| D | autofs.txt | 60 mount is considered to be *indirect*), then the root directory is
111 mounting onto a directory is considered to be "beyond a `stat`", the
200 initiated or is being considered, otherwise it returns 0.
266 and should be considered as deprecated for Sun Format automount maps.
276 only the `last_used` time is ever considered.
315 process in that process group is considered to come from the daemon.
|
| /Linux-v5.4/lib/ |
| D | dynamic_queue_limits.c | 39 * Queue considered starved if: in dql_completed()
60 * A decrease is only considered if the queue has been busy in in dql_completed()
|
| /Linux-v5.4/Documentation/devicetree/bindings/usb/ |
| D | mediatek,mtu3.txt | 31 it's considered valid for compatibility reasons, not allowed for
35 it's considered valid for compatibility reasons, not allowed for
|
| /Linux-v5.4/Documentation/driver-api/ |
| D | s390-drivers.rst | 26 not strictly considered I/O devices. They are considered here as well,
|
| /Linux-v5.4/Documentation/devicetree/bindings/mfd/ |
| D | aspeed-gfx.txt | 4 participates in pinmux requests on the g5 SoCs. It is therefore considered a
|
12345678910>>...39
