| /openbmc/qemu/tests/qapi-schema/ |
| H A D | alternate-clash.json | 1 # Alternate branch name collision
2 # Naming rules make collision impossible (even with the pragma). If
3 # that wasn't the case, then we'd get a collision in generated C: two
|
| H A D | reserved-type-list.json | 1 # Potential C name collision
3 # TODO - we could choose array names to avoid collision with user types,
|
| H A D | reserved-member-has.json | 1 # C member name collision
4 # TODO we could munge the optional flag name to avoid the collision.
|
| H A D | reserved-member-u.json | 1 # Potential C member name collision
6 # TODO - we could munge the member name to 'q_u' to avoid the collision
|
| H A D | reserved-command-q.json | 1 # C entity name collision
|
| H A D | reserved-enum-q.json | 1 # C entity name collision
|
| H A D | reserved-member-q.json | 1 # C member name collision
|
| H A D | struct-member-name-clash.json | 1 # C member name collision
|
| H A D | reserved-member-underscore.json | 1 # C member name collision
|
| H A D | struct-base-clash-deep.json | 3 # indirectly for the grandparent base; the collision doesn't care that
|
| H A D | qapi-schema-test.json | 78 # Among other things, test that a name collision between branches does
|
| /openbmc/u-boot/arch/arm/dts/ |
| H A D | zynqmp-zcu102-revB.dts | 29 /* Fix collision with u61 */
|
| /openbmc/linux/arch/arm64/boot/dts/xilinx/ |
| H A D | zynqmp-zcu102-revB.dts | 36 /* Fix collision with u61 */
|
| /openbmc/openbmc/meta-openembedded/meta-networking/recipes-protocols/zeroconf/ |
| H A D | zeroconf_0.9.bb | 8 Addresses are assigned randomly by each host and, in case of collision, \
|
| /openbmc/linux/fs/fscache/ |
| H A D | volume.c | 187 goto collision; in fscache_hash_volume()
203 collision: in fscache_hash_volume()
|
| H A D | cookie.c | 415 goto collision; in fscache_hash_cookie()
434 collision: in fscache_hash_cookie()
|
| /openbmc/linux/Documentation/networking/device_drivers/ethernet/3com/ |
| H A D | 3c509.rst | 211 0x02 Out-of-window collision.
230 Out of window collision. This typically occurs when some other Ethernet
237 or when another host doesn't correctly back off after a collision. If this
|
| /openbmc/linux/fs/smb/client/ |
| H A D | smb1ops.c | 167 bool collision, reconnect = false; in cifs_get_next_mid() local
193 collision = false; in cifs_get_next_mid()
203 collision = true; in cifs_get_next_mid()
221 if (!collision) { in cifs_get_next_mid()
|
| /openbmc/linux/Documentation/ABI/testing/ |
| H A D | sysfs-class-net-statistics | 132 a medium collision). See the network driver for the exact
215 due to a window collision. The specific meaning depends on the
|
| /openbmc/openbmc/poky/meta/recipes-core/util-linux/util-linux/ |
| H A D | libfdisk-cfdisk-and-sfdisk-sector-size-improvements.patch | 38 free(cxt->collision);
39 cxt->collision = NULL;
|
| /openbmc/openbmc/meta-openembedded/meta-filesystems/recipes-utils/f2fs-tools/f2fs-tools/ |
| H A D | 0002-f2fs_io-Define-_FILE_OFFSET_BITS-64.patch | 47 * collision exceeds
|
| /openbmc/linux/drivers/perf/ |
| H A D | xgene_pmu.c | 350 XGENE_PMU_EVENT_ATTR(in-rd-collision, 0x0e),
351 XGENE_PMU_EVENT_ATTR(in-wr-collision, 0x0f),
352 XGENE_PMU_EVENT_ATTR(collision-queue-not-empty, 0x10),
353 XGENE_PMU_EVENT_ATTR(collision-queue-full, 0x11),
|
| /openbmc/linux/Documentation/locking/ |
| H A D | futex-requeue-pi.rst | 107 result of a high-speed collision between futex_wait() and
|
| /openbmc/linux/Documentation/usb/ |
| H A D | gadget_multi.rst | 103 so there will be no collision with other customised gadgets or the
|
| /openbmc/linux/tools/perf/Documentation/ |
| H A D | perf-arm-spe.txt | 89 When an operation is sampled while a previous sampled operation has not finished, a collision
|