Searched full:colliding (Results 1 – 25 of 30) sorted by relevance
12
| /linux/Documentation/devicetree/bindings/net/wireless/ |
| H A D | qcom,ath11k-pci.yaml | 29 with colliding bus and device ids
36 with colliding bus and device ids
|
| H A D | qcom,ath12k-wsi.yaml | 59 with colliding bus and device ids
66 with colliding bus and device ids
|
| H A D | qcom,ath10k.yaml | 112 for designs with colliding bus and device specific ids
119 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
55 board-2.bin for designs with colliding bus and device specific ids
|
| /linux/include/uapi/linux/usb/ |
| H A D | g_hid.h | 33 * Don't add any colliding codes to either driver, and keep
|
| 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
|
| /linux/fs/xfs/ |
| H A D | xfs_trans_priv.h | 35 * This means a traversal colliding with a removal will cause a restart of the
|
| /linux/fs/nfs/ |
| H A D | namespace.c | 139 * colliding, and to allow "df" to work properly.
|
| /linux/tools/testing/selftests/net/netfilter/ |
| H A D | nft_nat_zones.sh | 29 # namespaces. Each client connects to Server, each with colliding tuples:
|
| /linux/Documentation/filesystems/ext4/ |
| H A D | directory.rst | 222 case where these two (or more) hash-colliding entries do not fit into one leaf
|
| /linux/fs/ubifs/ |
| H A D | debug.c | 1185 * dbg_check_key_order - make sure that colliding keys are properly ordered.
1190 * In UBIFS indexing B-tree colliding keys has to be sorted in binary order of
1266 ubifs_err(c, "bad order of colliding key %s", in dbg_check_key_order()
1413 /* This can only be keys with colliding hash */ in dbg_check_znode()
1423 * Colliding keys should follow binary order of in dbg_check_znode()
|
| H A D | tnc_misc.c | 402 /* These can only be keys with colliding hash */ in read_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()
|
| /linux/net/netfilter/ |
| H A D | nf_nat_core.c | 272 * If ignored_conntrack and colliding ct are not subject to NAT then in nf_nat_used_tuple_new()
369 * action: evict colliding if its in timewait state and the in nf_nat_used_tuple_harder()
|
| H A D | nf_conntrack_core.c | 1155 * If @skb has no NAT transformation or if the colliding entries are
|
| /linux/Documentation/PCI/ |
| H A D | pci.rst | 250 The idea is to prevent two devices colliding on the same address range.
|
| /linux/mm/ |
| H A D | mmu_notifier.c | 201 * invalidate_start/end and is colliding. in mmu_interval_read_begin()
|
| /linux/tools/testing/selftests/kvm/arm64/ |
| H A D | vgic_init.c | 328 TEST_ASSERT(ret && errno == EINVAL, "register redist region colliding with dist"); in subtest_v3_redist_regions()
|
| /linux/net/ceph/crush/ |
| H A D | mapper.c | 489 /* keep trying until we get a non-out, non-colliding item */ in crush_choose_firstn()
|
| /linux/drivers/md/dm-vdo/indexer/ |
| H A D | index.c | 559 * later return stale advice if there is a colliding name in the same chapter, but it's a in remove_from_index_zone()
|
| /linux/net/l2tp/ |
| H A D | l2tp_core.c | 407 /* If no match found, the colliding session ID isn't in our in l2tp_v3_session_get_next()
|
| /linux/net/sunrpc/ |
| H A D | xprt.c | 262 * transport connects from colliding with writes. No congestion control
|
| /linux/net/ipv6/ |
| H A D | ndisc.c | 861 * We are colliding with another node in ndisc_recv_ns()
|
| /linux/arch/x86/kvm/ |
| H A D | xen.c | 1385 * KVM by colliding with a real MSR that requires special handling. in kvm_xen_hvm_config()
|
12