/openbmc/linux/Documentation/admin-guide/blockdev/drbd/ |
H A D | disk-states-8.dot | 3 Diskless -> Consistent [ label = "ioctl_set_disk()" ] 5 Consistent -> Outdated [ label = "receive_param()" ] 6 Consistent -> UpToDate [ label = "receive_param()" ] 7 Consistent -> Inconsistent [ label = "start resync" ] 11 Consistent -> Failed [ label = "io completion error" ]
|
/openbmc/qemu/tests/qemu-iotests/ |
H A D | 296.out | 5 {"error": {"class": "GenericError", "desc": "Failed to get shared \"consistent read\" lock"}} 6 {"error": {"class": "GenericError", "desc": "Failed to get shared \"consistent read\" lock"}} 10 qemu-img: Failed to get shared "consistent read" lock 15 {"error": {"class": "GenericError", "desc": "Failed to get shared \"consistent read\" lock"}} 16 {"error": {"class": "GenericError", "desc": "Failed to get shared \"consistent read\" lock"}}
|
H A D | 273.out | 208 "consistent-read" 213 "consistent-read" 224 "consistent-read" 235 "consistent-read" 238 "consistent-read" 249 "consistent-read"
|
/openbmc/linux/tools/testing/selftests/bpf/progs/ |
H A D | cgroup_tcp_skb.c | 201 * are consistent with the state of the server socket. 224 * are consistent with the state of the server socket. 247 * are consistent with the state of the server socket. 270 * are consistent with the state of the server socket. 293 * are consistent with the state of the client socket. 316 * are consistent with the state of the client socket. 339 * are consistent with the state of the client socket. 362 * are consistent with the state of the client socket.
|
/openbmc/linux/drivers/comedi/drivers/ni_routing/ |
H A D | README | 18 2) The register values are _NOT_ completely consistent. There is no way to 29 4) The sets of routes that are valid are not consistent from device to device. 33 through any documentation. In fact, the only consistent source of this 48 directory are chosen to be consistent with (a) the NI's user level 96 As noted above, the only known consistent source of information for 119 As noted above, the only consistent source of information of valid 178 convention, although the register values are not consistent. This next table
|
/openbmc/linux/Documentation/core-api/ |
H A D | dma-api-howto.rst | 158 SN2) requires 64-bit consistent allocations to operate correctly when the IO 177 The setup for consistent allocations is performed via a call 224 uses consistent allocations, one would have to check the return value from 281 - Consistent DMA mappings which are usually mapped at driver 287 Think of "consistent" as "synchronous" or "coherent". 289 The current default is to return consistent memory in the low 32 291 set the consistent mask even if this default is fine for your 294 Good examples of what to use consistent mappings for are: 303 versa. Consistent mappings guarantee this. 307 Consistent DMA memory does not preclude the usage of [all …]
|
H A D | dma-api.rst | 11 Part II describes extensions for supporting non-consistent memory 13 non-consistent platforms (this is usually only legacy platforms) you 36 Consistent memory is memory for which a write by either the device or 42 This routine allocates a region of <size> bytes of consistent memory. 51 Note: consistent memory can be expensive on some platforms, and the 53 consolidate your requests for consistent memory as much as possible. 67 Free a region of consistent memory you previously allocated. dev,
|
/openbmc/linux/arch/powerpc/mm/ |
H A D | dma-noncoherent.c | 3 * PowerPC version derived from arch/arm/mm/consistent.c 20 * make an area consistent. 91 * __dma_sync_page makes memory consistent. identical to __dma_sync, but
|
/openbmc/openbmc/poky/meta/files/common-licenses/ |
H A D | Hippocratic-2.1 | 5 …d above to permit the Licensee (as defined below) broad permission, if consistent with Human Right… 17 …Human Rights Principles”). Licensee shall use the Software in a manner consistent with Human Right… 19 …validity of Section 1(a) or (ii) a determination of whether any Law is consistent or in conflict w… 23 … due process, or similar rights; provided, however, that such Laws are consistent and not in confl…
|
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-test/cunit/files/ |
H A D | fixup-install-docdir.patch | 6 header files in locations not consistent with the OE filesystem layout. 7 So here we specify new locations which are consistent with OE filesystems.
|
/openbmc/linux/Documentation/scheduler/ |
H A D | sched-nice-design.rst | 58 To sum it up: we always wanted to make nice levels more consistent, but 93 it was possible to implement better and more consistent nice +19 98 To address the second complaint (of nice levels not being consistent),
|
/openbmc/linux/fs/btrfs/ |
H A D | Kconfig | 59 state of the filesystem on disk is always consistent, i.e., 61 in a consistent state.
|
/openbmc/phosphor-led-manager/ |
H A D | README.md | 27 to always be consistent, Group Priority can be used to enforce the consistent
|
/openbmc/docs/designs/ |
H A D | device-tree-gpio-naming.md | 19 for these GPIO names and if you want userspace code to be able to be consistent 20 across different machines, these names would need to be consistent. 210 pin number. This removes a dependency on the device tree to have consistent
|
H A D | ocp-led-policy-support.md | 118 consistent state. The indicator state must be consistent even when conflicting 133 be in a consistent state. The change can be done in a backwards-compatible way.
|
/openbmc/hiomapd/ |
H A D | README.md | 63 and have consistent approaches to solving problems. 82 restriction that the method must be consistent between C and C++:
|
/openbmc/qemu/scripts/ |
H A D | render_block_graph.py | 34 s += 'r' if 'consistent-read' in arr else '_' 58 ' r - consistent-Read\l'
|
/openbmc/phosphor-mboxd/ |
H A D | README.md | 83 and have consistent approaches to solving problems. 101 restriction that the method must be consistent between C and C++:
|
/openbmc/linux/arch/microblaze/mm/ |
H A D | Makefile | 6 obj-y := consistent.o init.o pgtable.o mmu_context.o fault.o
|
/openbmc/qemu/tests/qapi-schema/ |
H A D | doc-bad-indent.json | 1 # Multiline doc comments should have consistent indentation
|
/openbmc/linux/drivers/video/ |
H A D | hdmi.c | 85 * Validates that the infoframe is consistent and updates derived fields 191 * Validates that the infoframe is consistent and updates derived fields 256 * Validates that the infoframe is consistent and updates derived fields 325 * Validates that the infoframe is consistent and updates derived fields 380 * Validates that the infoframe is consistent and updates derived fields 466 * Validates that the infoframe is consistent and updates derived fields 584 * Validates that the infoframe is consistent and updates derived fields 664 * Validates that the infoframe is consistent and updates derived fields 732 * Validates that the infoframe is consistent. 818 * Validates that the infoframe is consistent and updates derived fields [all …]
|
/openbmc/linux/include/linux/ |
H A D | u64_stats_sync.h | 27 * are consistent w.r.t. each other (remember point #2: seqcounts are not 46 * While a consumer (reader) should use following template to get consistent
|
/openbmc/u-boot/doc/ |
H A D | README.fsl-dpaa | 10 which 10GEC enumeration is consistent with MAC enumeration.
|
/openbmc/openbmc/poky/meta/recipes-multimedia/alsa/ |
H A D | alsa-plugins_1.2.12.bb | 16 # consistent with the libsamplerate license. However, if the licensee has a 62 # /etc to be consistent with other installed configuration 87 # plugins in a consistent way).
|
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-devtools/editorconfig/ |
H A D | editorconfig-core-c_0.12.9.bb | 1 SUMMARY = "EditorConfig helps maintain consistent coding styles across various editors and IDEs."
|