| /openbmc/openbmc/poky/bitbake/lib/toaster/tests/browser/ |
| H A D | test_builddashboard_page_artifacts.py | 73 msg = 'Images option should not be shown in left-hand menu'
78 If a build produced SDK artifacts, they should be shown, but the section
107 msg = 'Images option should not be shown in left-hand menu for ' \
120 'package count should not be shown for non-image builds')
124 'package size should not be shown for non-image builds')
133 they should all be shown, as well as the image link in the left-hand
136 The packages count and size should be shown, with a link to the
176 msg = 'Images option should be shown in left-hand menu for image builds'
203 'package count should be shown for image builds')
208 'package size should be shown for image builds')
|
| H A D | test_project_builds_page.py | 80 as shown in the main table of the page
108 """ "in progress" builds should not be shown in main table """
123 """ Task should be shown as suffixes on build names """
148 'should be no top bar shown for command line builds')
158 'should be a top bar shown for non-command-line builds')
|
| H A D | test_most_recent_builds_states.py | 46 # build queued; check shown as queued
85 # check status is shown as "Tasks starting..."
141 # all tasks complete and build succeeded; check success state shown
159 # all tasks complete and build succeeded; check fail state shown
|
| /openbmc/linux/Documentation/devicetree/bindings/ata/ |
| H A D | ceva,ahci-1v84.yaml | 44 The fields for the above parameter must be as shown below:-
56 The fields for the above parameter must be as shown below:-
68 The fields for the above parameter must be as shown below:-
80 The fields for the above parameter must be as shown below:-
90 The fields for the above parameter must be as shown below:-
102 The fields for the above parameter must be as shown below:-
114 The fields for the above parameter must be as shown below:-
126 The fields for the above parameter must be as shown below:-
|
| /openbmc/openbmc-test-automation/lib/ |
| H A D | ipmi_utils.py | 222 example is shown below:
232 For the data shown above, the following dictionary will be returned.
264 example is shown below:
287 For the data shown above, the following dictionary will be returned.
322 example is shown below:
336 For the data shown above, the following dictionary will be returned.
363 example is shown below:
372 For the data shown above, the SDR record type with 0xc0 count will be returned.
417 example is shown below:
436 For the data shown above, the following list of dictionaries will be
[all …]
|
| /openbmc/u-boot/doc/ |
| H A D | README.bootmenu | 31 <title> is the text of the menu entry shown on the console
44 will be CONFIG_BOOTDELAY. If delay is 0, no menu entries will be shown on
46 be called immediately. If delay is less then 0, bootmenu will be shown and
|
| /openbmc/openbmc/poky/bitbake/lib/toaster/toastergui/templates/ |
| H A D | editcustomimage_modal.html | 2 modal dialog shown on the build dashboard, for editing an existing custom image;
3 only shown if more than one custom image was built, so the user needs to
64 $("#edit-custom-image-modal").on("shown.bs.modal", function() {
|
| /openbmc/linux/Documentation/ABI/testing/ |
| H A D | sysfs-platform-asus-wmi | 136 Shown on Intel+Nvidia or AMD+Nvidia based systems:
146 on AMD. Shown on Intel+Nvidia or AMD+Nvidia based systems:
163 Set the APU SPPT limit. Shown on full AMD systems only:
171 Set the platform SPPT limit. Shown on full AMD systems only:
|
| /openbmc/linux/Documentation/trace/ |
| H A D | hisi-ptt.rst | 171 8 bit. Current supported types and related values are shown below:
187 supported are shown below:
195 shown below:
212 Current supported formats and related values are shown below:
220 (Header DW0-3 shown below). For example, the TLP header for Memory
221 Reads with 64-bit addresses is shown in PCIe r5.0, Figure 2-17;
222 the header for Configuration Requests is shown in Figure 2.20, etc.
|
| /openbmc/linux/tools/perf/Documentation/ |
| H A D | callchain-overhead-calculation.txt | 3 The overhead can be shown in two columns as 'Children' and 'Self' when
100 So '\_\_libc_start_main' and 'main' are shown first since they have
104 Since v3.16 the 'children' overhead is shown by default and the output
|
| /openbmc/linux/include/linux/sched/ |
| H A D | debug.h | 30 * task), SP is the stack pointer of the first frame that should be shown in the back
31 * trace (or NULL if the entire call-chain of the task should be shown).
|
| /openbmc/linux/include/linux/ |
| H A D | coda.h | 16 shown in the file LICENSE, or under the license shown below. The
|
| H A D | crc8.h | 47 * represented as shown below.
65 * represented as shown below.
|
| /openbmc/u-boot/doc/device-tree-bindings/misc/ |
| H A D | fs_loader.txt | 17 ubi in device tree source as shown in below:
20 sata and ubi as shown in below:
|
| /openbmc/openbmc-test-automation/ |
| H A D | CONTRIBUTING.md | 190 - As shown in the following example, if your keyword has any arguments,
195 description text as shown in the example below.
409 are a relative or absolute path (as shown in the examples above). A file
445 are a relative or absolute path (as shown in the examples above). A dir
491 coded in the order shown.
564 - As shown in the prior example, if your function has any arguments, include a
766 a relative or absolute path (as shown in the examples above). A file path
801 a relative or absolute path (as shown in the examples above). A dir path
|
| /openbmc/pldm/pldmtool/ |
| H A D | README.md | 49 with the **-h** help option as shown below:
97 command name with **-h** argument as shown below.
244 Enable verbosity with **-v** flag as shown below.
|
| /openbmc/linux/Documentation/RCU/Design/Memory-Ordering/ |
| H A D | Tree-RCU-Memory-Ordering.rst | 197 shown below, which is one of several functions that enforce ordering of
275 portion of RCU's grace period guarantee is shown in the following
285 period until a later call to ``rcu_accelerate_cbs()``, as shown in the
288 One set of code paths shown on the left invokes ``rcu_accelerate_cbs()``
342 counter, as shown below:
370 to the newly advanced value from the ``rcu_state`` structure, as shown
410 non-idle CPUs report their own quiescent states, as shown in the
425 its leaf ``rcu_node`` lock. Therefore, all execution shown in this
462 traverses up the ``rcu_node`` tree as shown at the bottom of the
486 effects are as shown below:
[all …]
|
| /openbmc/linux/Documentation/admin-guide/mm/ |
| H A D | ksm.rst | 158 The effectiveness of KSM and MADV_MERGEABLE is shown in ``/sys/kernel/mm/ksm/``:
223 ``ksm_zero_pages``, both of which are shown under the directory
224 ``/proc/<pid>/ksm_stat``, and ksm_rmap_items is also shown in
225 ``/proc/<pid>/ksm_stat``. The process profit is also shown in
|
| /openbmc/openbmc/meta-raspberrypi/docs/ |
| H A D | conf.py | 18 # documentation root, use os.path.abspath to make it absolute, like shown here.
103 # If true, sectionauthor and moduleauthor directives will be shown in the
205 # If true, "Created using Sphinx" is shown in the HTML footer. Default is True.
209 # If true, "(C) Copyright ..." is shown in the HTML footer. Default is True.
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-security/keyutils/files/ |
| H A D | 0002-tests-Use-head-n1-for-busybox-compatibility.patch | 21 # check the session keyring ID is shown
30 # check the session keyring ID is shown
|
| /openbmc/qemu/docs/system/ |
| H A D | images.rst | 63 A VM snapshot is made of a VM state info (its size is shown in
68 not shown by ``info snapshots`` because the associated disk sectors are
|
| /openbmc/linux/Documentation/sound/designs/ |
| H A D | procfile.rst | 110 shown also when the invalid H/W pointer is detected at the
197 ports. The connection status and the running status are shown
224 - set-up of PCM, shown in hw_parms, sw_params, and status in the PCM
|
| /openbmc/linux/tools/memory-model/Documentation/ |
| H A D | recipes.txt | 217 the desired MP ordering. The general approach is shown below:
248 pointers. The general approach is shown below:
276 (address dependency, as shown above), the value written by a later store
293 to understand their use cases. The general approach is shown below:
381 The A/D pairing from the ring-buffer use case shown earlier also
495 values of 0, but providing both full barriers as shown above prevents
|
| /openbmc/docs/architecture/ |
| H A D | interface-overview.md | 22 and service shown.
28 details from the unit file may be shown, such as the program which implements a
247 | | -+- many more (not shown here) |
263 This section lists each interface and service shown in this document. The intent
286 maintains a logically separate network from the host, as shown in this diagram:
306 direct connection external to the host, as shown in this diagram:
|
| /openbmc/openbmc/poky/meta/lib/bblayers/ |
| H A D | buildconf.py | 24 They will be shown to the users when they set up their builds via TEMPLATECONF.
27 It will be shown to the users when they set up their builds via TEMPLATECONF.
|