| /linux/Documentation/maintainer/ |
| A 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/Documentation/ABI/testing/ |
| A D | sysfs-bus-iio-proximity | 8 considered close to the device. If the value read from the
10 should typically be considered near.
|
| A 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/Documentation/devicetree/bindings/iio/ |
| A 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/Documentation/devicetree/bindings/input/ |
| A D | adc-keys.txt | 9 considered up.
22 considered pressed.
|
| /linux/Documentation/xtensa/ |
| 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.
|
| 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/devicetree/bindings/display/panel/ |
| A 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/include/trace/events/ |
| A D | compaction.h | 254 __field(unsigned int, considered)
263 __entry->considered = zone->compact_considered;
273 __entry->considered,
|
| /linux/Documentation/power/ |
| A 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/Documentation/admin-guide/hw-vuln/ |
| 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/admin-guide/device-mapper/ |
| 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/process/ |
| A 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/Documentation/dev-tools/ |
| A 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/Documentation/devicetree/bindings/cpu/ |
| A 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/Documentation/devicetree/bindings/mfd/ |
| A D | aspeed-gfx.txt | 4 participates in pinmux requests on the g5 SoCs. It is therefore considered a
|
| A D | twl-family.txt | 17 it is considered as an interrupt controller cascaded to the SoC one.
|
| /linux/Documentation/mhi/ |
| 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/translations/zh_CN/process/ |
| A D | index.rst | 56 volatile-considered-harmful
|
| A D | volatile-considered-harmful.rst | 5 :Original: :ref:`Documentation/process/volatile-considered-harmful.rst
|
| /linux/Documentation/devicetree/bindings/w1/ |
| A D | w1-gpio.yaml | 25 If specified, the data pin is considered in open-drain mode.
|
| /linux/Documentation/devicetree/bindings/net/ |
| A 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/Documentation/translations/zh_TW/process/ |
| A D | index.rst | 59 volatile-considered-harmful
|
| A D | volatile-considered-harmful.rst | 7 :Original: :ref:`Documentation/process/volatile-considered-harmful.rst
|
| /linux/Documentation/block/ |
| A D | pr.rst | 44 All initiators with a registered key are considered reservation
51 All initiators with a registered key are considered reservation
|