Searched full:colliding (Results 1 – 25 of 27) sorted by relevance
12
| /Linux-v6.1/include/uapi/linux/usb/ |
| D | g_printer.h | 30 * Don't add any colliding codes to either driver, and keep
|
| D | gadgetfs.h | 66 * Don't add any colliding codes to either driver, and keep
|
| /Linux-v6.1/arch/arm64/kernel/pi/ |
| D | kaslr_early.c | 106 * the lower and upper quarters to avoid colliding with other in kaslr_early_init()
|
| /Linux-v6.1/fs/xfs/ |
| D | xfs_trans_priv.h | 38 * This means a traversal colliding with a removal will cause a restart of the
|
| /Linux-v6.1/fs/nfs/ |
| D | namespace.c | 139 * colliding, and to allow "df" to work properly.
|
| /Linux-v6.1/tools/testing/selftests/netfilter/ |
| D | nft_nat_zones.sh | 29 # namespaces. Each client connects to Server, each with colliding tuples:
|
| /Linux-v6.1/Documentation/devicetree/bindings/net/wireless/ |
| D | qcom,ath11k.yaml | 48 board-2.bin for designs with colliding bus and device specific ids
|
| /Linux-v6.1/drivers/net/wireless/intel/iwlwifi/fw/ |
| D | error-dump.h | 231 /* Use bit 31 as dump info type to avoid colliding with region types */
|
| /Linux-v6.1/fs/ubifs/ |
| D | tnc_misc.c | 380 /* These can only be keys with colliding hash */ in read_znode()
|
| 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()
|
| D | tnc.c | 1251 * splitting in the middle of the colliding sequence. Also, when in ubifs_lookup_level0()
1876 * them look at each direntry with colliding name hash sequentially. in ubifs_tnc_lookup_nm()
1981 * them look at each direntry with colliding name hash sequentially. in ubifs_tnc_lookup_dh()
|
| /Linux-v6.1/tools/testing/selftests/kvm/aarch64/ |
| D | vgic_init.c | 318 TEST_ASSERT(ret && errno == EINVAL, "register redist region colliding with dist"); in subtest_v3_redist_regions()
|
| /Linux-v6.1/Documentation/PCI/ |
| D | pci.rst | 250 The idea is to prevent two devices colliding on the same address range.
|
| /Linux-v6.1/mm/ |
| D | mmu_notifier.c | 199 * invalidate_start/end and is colliding. in mmu_interval_read_begin()
|
| /Linux-v6.1/net/ceph/crush/ |
| D | mapper.c | 485 /* keep trying until we get a non-out, non-colliding item */ in crush_choose_firstn()
|
| /Linux-v6.1/arch/microblaze/pci/ |
| D | pci-common.c | 637 * resource flags as if they were colliding in pcibios_allocate_bus_resources()
|
| /Linux-v6.1/drivers/scsi/aic7xxx/ |
| D | aic7xxx.h | 149 * time. To avoid colliding with a DMA write from the sequencer,
|
| /Linux-v6.1/kernel/time/ |
| D | posix-cpu-timers.c | 718 * We are colliding with the timer actually firing. in posix_cpu_timer_set()
|
| /Linux-v6.1/net/sunrpc/ |
| D | xprt.c | 262 * transport connects from colliding with writes. No congestion control
|
| /Linux-v6.1/net/ipv6/ |
| D | ndisc.c | 867 * We are colliding with another node in ndisc_recv_ns()
|
| /Linux-v6.1/net/netfilter/ |
| D | nf_conntrack_core.c | 1111 * If @skb has no NAT transformation or if the colliding entries are
|
| /Linux-v6.1/arch/x86/kvm/svm/ |
| D | sev.c | 1621 * Reset the role to one that avoids colliding with in sev_lock_vcpus_for_migration()
|
| /Linux-v6.1/drivers/gpu/drm/i915/ |
| D | intel_uncore.c | 201 * There is a possibility of driver's wake request colliding in fw_domain_wait_ack_with_fallback()
|
| /Linux-v6.1/drivers/net/ethernet/intel/ |
| D | e100.c | 84 * In order to keep updates to the RFD link field from colliding with
|
| /Linux-v6.1/drivers/tty/ |
| D | n_gsm.c | 1670 * us from colliding with another sender or a receive completion event.
|
12
