Home
last modified time | relevance | path

Searched full:differing (Results 1 – 25 of 50) sorted by relevance

12

/linux/include/linux/
H A Dtrace_clock.h6 * 3 trace clock variants, with differing scalability/precision
/linux/net/dcb/
H A DKconfig12 NICs and switches to support network traffic with differing
/linux/security/lockdown/
H A DKconfig24 The kernel can be configured to default to differing levels of
/linux/Documentation/process/
H A Dcode-of-conduct.rst23 * Being respectful of differing viewpoints and experiences
H A Dhowto.rst457 there will always be differing opinions on how beneficial a patch is.
/linux/Documentation/arch/arm64/
H A Dtagged-pointers.rst88 likely that C compilers will not hazard two virtual addresses differing
/linux/tools/testing/selftests/drivers/net/hw/
H A Dcsum.py51 Most tests follow the same basic pattern, differing only in
/linux/drivers/mtd/tests/
H A Dtorturetest.c446 * Count the number of differing bytes and bits and return the first differing
/linux/kernel/trace/
H A Dtrace_clock.c7 * Implements 3 trace clock variants, with differing scalability/precision
/linux/tools/testing/selftests/bpf/progs/
H A Dcore_reloc_types.h492 } c __bpf_aligned; /* inline enum def with differing set of values */
847 * offset, but with differing final relocation values: size 4 vs size 1
1268 /* differing enumerator values */
/linux/tools/lib/perf/include/internal/
H A Devsel.h65 * Whilst it is possible to combine events into a group with differing
/linux/arch/arm/mm/
H A DKconfig1104 memory with differing types results in unpredictable behaviour,
1107 Multiple mappings with differing attributes is also unpredictable
/linux/Documentation/filesystems/
H A Djournalling.rst78 journal. Since transactions can't be nested/batched across differing
/linux/Documentation/devicetree/bindings/cpu/
H A Dcpu-capacity.txt22 context is about differing performance characteristics; this binding tries to
/linux/Documentation/leds/
H A Dleds-class.rst69 be required for given platform, differing only with an ordinal number.
/linux/drivers/gpu/drm/i915/
H A Di915_gem_gtt.c88 * differing domains). See i915_gem_evict_for_node() for the gory details
/linux/include/xen/interface/
H A Dplatform.h61 * of overlapping memory regions with differing types). If it is not known
/linux/net/rxrpc/
H A Dlocal_object.c55 * conflicting uses by differing services. Further, we don't want to share
/linux/drivers/input/misc/
H A Dpowermate.c57 /* at least two versions of the hardware exist, with differing payload
/linux/arch/arm64/kernel/
H A Dcpufeature.c466 * Differing PARange is fine as long as all peripherals and memory are mapped
533 * Linux can handle differing I-cache policies. Userspace JITs will
535 * If we have differing I-cache policies, report it as the weakest - VIPT.
1373 * The kernel can handle differing I-cache policies, but otherwise in update_cpu_features()
1416 * Differing PARange support is fine as long as all peripherals and in update_cpu_features()
/linux/arch/arm64/kvm/
H A Dnested.c626 * - S2 being enabled or not, hence differing by the HCR_EL2.VM bit
628 * - Multiple vcpus using private S2s (huh huh...), hence differing by the
/linux/drivers/net/phy/
H A Dsfp-bus.c295 * 1310nm/1550nm) are not 1000BASE-BX compliant due to the differing in sfp_module_parse_support()
/linux/scripts/kconfig/
H A Dmenu.c656 * differing dependencies and visibility. In these rare cases, we in get_prompt_str()
/linux/include/rdma/
H A Drdmavt_qp.h318 * the driver can have differing an potentially
/linux/drivers/nvme/host/
H A Dnvme.h43 * path in the future to accommodate architectures with differing

12