| /openbmc/linux/Documentation/maintainer/ |
| H 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.
|
| /openbmc/webui-vue/.github/ISSUE_TEMPLATE/ |
| H A D | feature_request.md | 15 **Describe alternatives you've considered** A clear and concise description of
16 any alternative solutions or features you've considered.
|
| /openbmc/u-boot/Licenses/ |
| H A D | Exceptions | 7 exactly for this purpose - this is merely considered normal use of
12 files in another file is considered normal use of U-Boot, and does
|
| /openbmc/linux/Documentation/ABI/testing/ |
| H A D | sysfs-bus-iio-proximity | 8 considered close to the device. If the value read from the
10 should typically be considered near.
|
| /openbmc/linux/Documentation/process/ |
| H A D | contribution-maturity-model.rst | 58 * A Software Engineer’s upstream code contributions will be considered
69 ACM, etc.), are considered part of an engineer’s work.
70 * A Software Engineer’s community contributions will be considered in
104 * Upstream kernel development is considered a formal job position, with
|
| /openbmc/linux/Documentation/arch/xtensa/ |
| H 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.
|
| H 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
|
| /openbmc/linux/include/trace/events/ |
| H A D | compaction.h | 249 __field(unsigned int, considered)
258 __entry->considered = zone->compact_considered;
268 __entry->considered,
|
| /openbmc/u-boot/doc/device-tree-bindings/memory/ |
| H A D | memory.txt | 8 that the result should have for the match to be considered valid. The mask
26 node to be considered a match.
|
| /openbmc/openbmc/poky/meta/files/common-licenses/ |
| H A D | MakeIndex | 17 …considered a modified version of this program under the requirement above. Ports of this program …
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-extended/tipcutils/tipcutils/ |
| H A D | 0001-test-ptts-Set-recv-buffer-size-too-max-to-receive-as.patch | 7 Flooding multicast may make the rcv buffer overrun and is considered
54 + * Flooding multicast may make the rcv buffer overrun and considered premature msg…
|
| /openbmc/linux/Documentation/devicetree/bindings/mfd/ |
| H A D | aspeed-gfx.txt | 4 participates in pinmux requests on the g5 SoCs. It is therefore considered a
|
| /openbmc/linux/Documentation/admin-guide/device-mapper/ |
| H 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.
|
| /openbmc/linux/Documentation/power/ |
| H 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
|
| /openbmc/openbmc/poky/documentation/dev-manual/ |
| H A D | vulnerabilities.rst | 254 is found in the name of the file, the corresponding CVE is considered as patched.
256 one is considered. Then, the code looks for ``CVE: CVE-ID`` lines in the patch
257 file. The found CVE IDs are also considered as patched.
259 and these are also considered as patched.
265 :term:`CVE_CHECK_SKIP_RECIPE`, it is considered as ``Patched``.
272 already considered as ``Patched``.
276 is considered as ``Unpatched``.
|
| /openbmc/phosphor-time-manager/ |
| H A D | meson.options | 14 # otherwise default value will be considered
|
| /openbmc/linux/Documentation/admin-guide/hw-vuln/ |
| H 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
|
| /openbmc/u-boot/board/keymile/km_arm/ |
| H A D | kwbimage_256M8_1.cfg | 200 # with the considered SDRAM internal delay
202 # with the considered SDRAM internal delay
209 # with the considered SDRAM internal delay
211 # with the considered SDRAM internal delay
|
| H A D | kwbimage_128M16_1.cfg | 200 # with the considered SDRAM internal delay
202 # with the considered SDRAM internal delay
209 # with the considered SDRAM internal delay
211 # with the considered SDRAM internal delay
|
| /openbmc/linux/Documentation/translations/zh_CN/process/ |
| H A D | index.rst | 56 volatile-considered-harmful
|
| /openbmc/linux/Documentation/translations/zh_TW/process/ |
| H A D | index.rst | 58 volatile-considered-harmful
|
| /openbmc/linux/Documentation/dev-tools/ |
| H 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().
|
| /openbmc/linux/Documentation/devicetree/bindings/cpu/ |
| H 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.
|
| /openbmc/openbmc/poky/meta/recipes-extended/diffutils/diffutils/ |
| H A D | 0001-Skip-strip-trailing-cr-test-case.patch | 7 work, but valgrind is considered too heavy-weight for diffutils
|
| /openbmc/phosphor-power/phosphor-power-sequencer/docs/config_file/ |
| H A D | rail.md | 33 …_VOUT command. If one of the error bits is set, the rail pgood will be considered false. The defau…
34 …IT). If the output voltage is below this limit, the rail pgood will be considered false. The defau…
|