Searched full:considered (Results 1 – 25 of 244) sorted by relevance
12345678910
| /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.
|
| /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-kernel-iommu_groups | 35 are considered to be relaxable and safe.
|
| D | debugfs-cec-error-inj | 31 Other than these basic rules described above this ABI is not considered
|
| D | sysfs-uevent | 20 format where 'x' is a hex digit. The UUID is considered to be
|
| /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
|
| /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.
|
| /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
|
| /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.
|
| D | index.rst | 60 volatile-considered-harmful
|
| /Documentation/devicetree/bindings/mfd/ |
| D | aspeed-gfx.txt | 4 participates in pinmux requests on the g5 SoCs. It is therefore considered a
|
| D | twl-family.txt | 17 it is considered as an interrupt controller cascaded to the SoC one.
|
| /Documentation/devicetree/bindings/w1/ |
| D | w1-gpio.txt | 13 - linux,open-drain: if specified, the data pin is considered in
|
| /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
|
| /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().
|
| /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
|
| /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.
|
| /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.
|
| /Documentation/translations/zh_CN/process/ |
| D | index.rst | 56 volatile-considered-harmful
|
| /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
|
| /Documentation/devicetree/bindings/sound/ |
| D | tdm-slot.txt | 28 number is considered 1 and 0 is 0. snd_soc_of_xlate_tdm_slot_mask()
|
| /Documentation/devicetree/bindings/input/ |
| D | adc-keys.txt | 8 - keyup-threshold-microvolt: Voltage at which all the keys are considered up.
|
| /Documentation/ABI/stable/ |
| D | vdso | 29 ABI of those symbols is considered stable. It may vary across architectures,
|
| /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
|
| /Documentation/translations/it_IT/process/ |
| D | index.rst | 60 volatile-considered-harmful
|
12345678910