Home
last modified time | relevance | path

Searched full:colliding (Results 1 – 25 of 55) sorted by relevance

123

/kernel/linux/linux-5.10/include/uapi/linux/usb/
Dg_printer.h30 * Don't add any colliding codes to either driver, and keep
Dgadgetfs.h66 * Don't add any colliding codes to either driver, and keep
/kernel/linux/linux-6.6/include/uapi/linux/usb/
Dg_printer.h30 * Don't add any colliding codes to either driver, and keep
Dgadgetfs.h66 * Don't add any colliding codes to either driver, and keep
/kernel/linux/linux-6.6/Documentation/devicetree/bindings/net/wireless/
Dqcom,ath11k-pci.yaml28 with colliding bus and device ids
Dqcom,ath10k.yaml99 for designs with colliding bus and device specific ids
Dqcom,ath11k.yaml48 board-2.bin for designs with colliding bus and device specific ids
/kernel/linux/linux-6.6/arch/arm64/kernel/pi/
Dkaslr_early.c106 * the lower and upper quarters to avoid colliding with other in kaslr_early_init()
/kernel/linux/linux-6.6/fs/xfs/
Dxfs_trans_priv.h38 * This means a traversal colliding with a removal will cause a restart of the
/kernel/linux/linux-5.10/fs/xfs/
Dxfs_trans_priv.h36 * This means a traversal colliding with a removal will cause a restart of the
/kernel/linux/linux-6.6/drivers/net/wireless/intel/iwlwifi/fw/
Derror-dump.h243 /* 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 */
/kernel/linux/linux-5.10/arch/arm64/kernel/
Dkaslr.c142 * the lower and upper quarters to avoid colliding with other in kaslr_early_init()
/kernel/linux/linux-5.10/fs/nfs/
Dnamespace.c139 * colliding, and to allow "df" to work properly.
/kernel/linux/linux-6.6/fs/nfs/
Dnamespace.c139 * colliding, and to allow "df" to work properly.
/kernel/linux/linux-6.6/tools/testing/selftests/netfilter/
Dnft_nat_zones.sh29 # namespaces. Each client connects to Server, each with colliding tuples:
/kernel/linux/linux-5.10/drivers/net/wireless/intel/iwlwifi/fw/
Derror-dump.h288 /* Use bit 31 as dump info type to avoid colliding with region types */
/kernel/linux/linux-6.6/fs/ubifs/
Dtnc_misc.c380 /* These can only be keys with colliding hash */ in read_znode()
Ddebug.c1186 * dbg_check_key_order - make sure that colliding keys are properly ordered.
1191 * In UBIFS indexing B-tree colliding keys has to be sorted in binary order of
1267 ubifs_err(c, "bad order of colliding key %s", in dbg_check_key_order()
1414 /* This can only be keys with colliding hash */ in dbg_check_znode()
1424 * Colliding keys should follow binary order of in dbg_check_znode()
/kernel/linux/linux-5.10/fs/ubifs/
Dtnc_misc.c380 /* These can only be keys with colliding hash */ in read_znode()
Ddebug.c1186 * dbg_check_key_order - make sure that colliding keys are properly ordered.
1191 * In UBIFS indexing B-tree colliding keys has to be sorted in binary order of
1267 ubifs_err(c, "bad order of colliding key %s", in dbg_check_key_order()
1414 /* This can only be keys with colliding hash */ in dbg_check_znode()
1424 * Colliding keys should follow binary order of in dbg_check_znode()
/kernel/linux/linux-6.6/net/netfilter/
Dnf_nat_core.c276 * If ignored_conntrack and colliding ct are not subject to NAT then in nf_nat_used_tuple_new()
373 * action: evict colliding if its in timewait state and the in nf_nat_used_tuple_harder()
/kernel/linux/linux-5.10/drivers/lightnvm/
Dpblk-write.c450 * can align, which would result on metadata and data I/Os colliding. In in pblk_valid_meta_ppa()
/kernel/linux/linux-6.6/tools/testing/selftests/kvm/aarch64/
Dvgic_init.c329 TEST_ASSERT(ret && errno == EINVAL, "register redist region colliding with dist"); in subtest_v3_redist_regions()
/kernel/linux/linux-5.10/Documentation/PCI/
Dpci.rst249 The idea is to prevent two devices colliding on the same address range.
/kernel/linux/linux-6.6/Documentation/PCI/
Dpci.rst250 The idea is to prevent two devices colliding on the same address range.

123