/openbmc/linux/Documentation/devicetree/bindings/net/wireless/ |
H A D | qcom,ath11k-pci.yaml | 28 with colliding bus and device ids
|
H A D | qcom,ath10k.yaml | 99 for designs with colliding bus and device specific ids
|
H A D | qcom,ath11k.yaml | 48 board-2.bin for designs with colliding bus and device specific ids
|
/openbmc/linux/include/uapi/linux/usb/ |
H A D | g_printer.h | 30 * Don't add any colliding codes to either driver, and keep
|
H A D | gadgetfs.h | 66 * Don't add any colliding codes to either driver, and keep
|
/openbmc/linux/arch/arm64/kernel/pi/ |
H A D | kaslr_early.c | 106 * the lower and upper quarters to avoid colliding with other in kaslr_early_init()
|
/openbmc/linux/fs/xfs/ |
H A D | xfs_trans_priv.h | 38 * This means a traversal colliding with a removal will cause a restart of the
|
/openbmc/u-boot/include/configs/ |
H A D | rpi.h | 138 * large initrds before they start colliding with U-Boot.
|
/openbmc/linux/drivers/net/wireless/intel/iwlwifi/fw/ |
H A D | error-dump.h | 243 /* Use bit 31 as dump info type to avoid colliding with region types */ 246 /* Use bit 31 and bit 24 as dump name type to avoid colliding with region types */
|
/openbmc/linux/fs/nfs/ |
H A D | namespace.c | 139 * colliding, and to allow "df" to work properly.
|
/openbmc/linux/tools/testing/selftests/netfilter/ |
H A D | nft_nat_zones.sh | 29 # namespaces. Each client connects to Server, each with colliding tuples:
|
/openbmc/u-boot/fs/ubifs/ |
H A D | tnc_misc.c | 368 /* These can only be keys with colliding hash */ in read_znode()
|
H A D | debug.c | 1170 * dbg_check_key_order - make sure that colliding keys are properly ordered. 1175 * In UBIFS indexing B-tree colliding keys has to be sorted in binary order of 1251 ubifs_err(c, "bad order of colliding key %s", in dbg_check_key_order() 1398 /* This can only be keys with colliding hash */ in dbg_check_znode() 1408 * Colliding keys should follow binary order of in dbg_check_znode()
|
H A D | tnc.c | 1235 * splitting in the middle of the colliding sequence. Also, when in ubifs_lookup_level0() 1858 * them look at each direntry with colliding name hash sequentially. in ubifs_tnc_lookup_nm()
|
/openbmc/linux/fs/ubifs/ |
H A D | tnc_misc.c | 380 /* These can only be keys with colliding hash */ in read_znode()
|
H A D | debug.c | 1182 * dbg_check_key_order - make sure that colliding keys are properly ordered. 1187 * In UBIFS indexing B-tree colliding keys has to be sorted in binary order of 1263 ubifs_err(c, "bad order of colliding key %s", in dbg_check_key_order() 1410 /* This can only be keys with colliding hash */ in dbg_check_znode() 1420 * Colliding keys should follow binary order of in dbg_check_znode()
|
H A D | tnc.c | 1289 * splitting in the middle of the colliding sequence. Also, when in ubifs_lookup_level0() 1914 * them look at each direntry with colliding name hash sequentially. in ubifs_tnc_lookup_nm() 2019 * them look at each direntry with colliding name hash sequentially. in ubifs_tnc_lookup_dh()
|
/openbmc/openbmc/meta-openembedded/meta-multimedia/recipes-multimedia/pipewire/ |
H A D | pipewire_1.2.7.bb | 98 # libjack.so* files, thus colliding with the libpack package. This
|
/openbmc/linux/net/netfilter/ |
H A D | nf_nat_core.c | 276 * If ignored_conntrack and colliding ct are not subject to NAT then in nf_nat_used_tuple_new() 367 * action: evict colliding if its in timewait state and the in nf_nat_used_tuple_harder()
|
/openbmc/linux/tools/testing/selftests/kvm/aarch64/ |
H A D | vgic_init.c | 329 TEST_ASSERT(ret && errno == EINVAL, "register redist region colliding with dist"); in subtest_v3_redist_regions()
|
/openbmc/linux/Documentation/PCI/ |
H A D | pci.rst | 250 The idea is to prevent two devices colliding on the same address range.
|
/openbmc/linux/mm/ |
H A D | mmu_notifier.c | 199 * invalidate_start/end and is colliding. in mmu_interval_read_begin()
|
/openbmc/linux/net/ceph/crush/ |
H A D | mapper.c | 485 /* keep trying until we get a non-out, non-colliding item */ in crush_choose_firstn()
|
/openbmc/linux/drivers/scsi/aic7xxx/ |
H A D | aic7xxx.h | 149 * time. To avoid colliding with a DMA write from the sequencer,
|
/openbmc/linux/kernel/time/ |
H A D | posix-cpu-timers.c | 717 * We are colliding with the timer actually firing. in posix_cpu_timer_set()
|