Searched full:considered (Results 1 – 25 of 1941) sorted by relevance
12345678910>>...78
| /kernel/linux/linux-5.10/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.
|
| /kernel/linux/linux-5.10/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.
|
| /kernel/linux/linux-4.19/Documentation/power/ |
| D | power_supply_class.txt | 94 when battery considered "full"/"empty" at normal conditions. Yes, there is
109 battery considered full/empty.
115 charge when battery considered full/empty at given conditions (temperature,
161 TIME_TO_EMPTY - seconds left for battery to be considered empty (i.e.
163 TIME_TO_FULL - seconds left for battery to be considered full (i.e.
|
| /kernel/linux/linux-4.19/Documentation/dev-tools/ |
| D | kmemleak.rst | 85 An allocated block of memory is considered orphan if no pointer to its
89 block to a freeing function and therefore the block is considered a
95 considered orphan)
103 4. the remaining white objects are considered orphan and reported via
110 block is not considered a leak. One example is __vmalloc().
|
| /kernel/linux/linux-4.19/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.
|
| /kernel/linux/linux-5.10/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.
|
| /kernel/linux/linux-5.10/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
|
| /kernel/linux/linux-5.10/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.
|
| /kernel/linux/linux-5.10/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.
|
| /kernel/linux/linux-4.19/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.
|
| /kernel/linux/linux-5.10/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
|
| /kernel/linux/linux-5.10/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().
|
| /kernel/linux/linux-5.10/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
|
| /kernel/linux/linux-5.10/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()
|
| /kernel/linux/linux-4.19/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()
|
| /kernel/linux/linux-5.10/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.
|
| /kernel/linux/linux-4.19/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
|
| /kernel/linux/linux-4.19/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.
|
| /kernel/linux/linux-5.10/arch/mips/include/asm/mach-generic/ |
| D | spaces.h | 54 * Memory above this physical address will be considered highmem.
81 * Memory above this physical address will be considered highmem.
|
| /kernel/linux/linux-4.19/Documentation/device-mapper/ |
| D | dm-log.txt | 8 mirrors, a region would be considered dirty/inconsistent while you
11 Once all writes are complete, the region is considered clean again.
|
| /kernel/linux/linux-4.19/Documentation/translations/zh_CN/ |
| D | volatile-considered-harmful.txt | 1 Chinese translated version of Documentation/process/volatile-considered-harmful.rst
12 Documentation/process/volatile-considered-harmful.rst 的中文翻译
|
| /kernel/linux/linux-4.19/kernel/irq/ |
| D | timings.c | 75 * An interrupt is considered periodically stable if the interval of
100 * considered as an anomaly and is discarded. However, a normal
167 * apply. Values outside the interval are considered as an in irqs_update()
189 * The interrupt is considered stable enough to try to predict in irqs_update()
|
| /kernel/linux/linux-5.10/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
|
| /kernel/linux/linux-5.10/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
|
| /kernel/linux/linux-4.19/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
|
12345678910>>...78