Home
last modified time | relevance | path

Searched full:assumptions (Results 1 – 25 of 242) sorted by relevance

12345678910

/linux-6.12.1/scripts/dtc/libfdt/
Dlibfdt_internal.h79 * Defines assumptions which can be enabled. Each of these can be enabled
80 * individually. For maximum safety, don't enable any assumptions!
128 * assumptions about correctness.
189 /** helper macros for checking assumptions */
/linux-6.12.1/net/sunrpc/xprtrdma/
Dsvc_rdma_pcl.c90 * Assumptions:
141 * Assumptions:
193 * Assumptions:
257 * Assumptions:
/linux-6.12.1/Documentation/arch/x86/
Dkernel-stacks.rst83 assumptions about the previous state of the kernel stack.
92 avoids making assumptions about the previous state of the kernel
106 assumptions about the previous state of the kernel stack.
/linux-6.12.1/drivers/net/fddi/
Ddefxx.c352 * Assumptions:
425 * Assumptions:
522 * Assumptions:
711 * Assumptions:
872 * Assumptions:
935 * Assumptions:
1030 * Assumptions:
1158 * Note: If the assumptions change regarding the non-paged, non-cached, in dfx_driver_init()
1244 * Assumptions:
1441 * Assumptions:
[all …]
/linux-6.12.1/include/drm/
Ddrm_panic.h75 * Panic printing code can make the following assumptions while holding the
108 * Drivers must not make any assumptions about the actual state of the hardware,
/linux-6.12.1/arch/powerpc/include/asm/
Dcrashdump-ppc64.h9 * The implicit assumptions are:
/linux-6.12.1/Documentation/ABI/testing/
Dsysfs-devices-system-xen_cpu20 logic restrictions and assumptions.
/linux-6.12.1/arch/riscv/include/asm/
Dclint.h21 * like "riscv_mtime", to signify that these non-ISA assumptions must hold.
/linux-6.12.1/Documentation/i2c/
Dwriting-clients.rst124 monitoring chips on PC motherboards, and thus used to embed some assumptions
126 assumptions was that most adapters and devices drivers support the SMBUS_QUICK
131 and complex components such as DVB adapters, those assumptions became more
/linux-6.12.1/drivers/gpu/drm/msm/dp/
Ddp_link.h84 * Few simplistic rules and assumptions made here: in dp_link_bit_depth_to_bpp()
/linux-6.12.1/Documentation/arch/x86/x86_64/
Dfsgs.rst97 reason for this is that older kernels make assumptions about the values in
100 would violate these assumptions and cause malfunction.
/linux-6.12.1/drivers/net/ethernet/intel/i40e/
Di40e_hmc.c97 * assumptions:
177 * assumptions:
/linux-6.12.1/arch/mips/include/asm/mach-generic/
Dspaces.h76 * Fixme: 59 bits is a fictive number and makes assumptions about processors
/linux-6.12.1/drivers/staging/greybus/
Daudio_apbridgea.h10 * assumptions are made:
/linux-6.12.1/include/linux/
Dvirtio_config.h150 /* Did you forget to fix assumptions on max features? */ in __virtio_test_bit()
167 /* Did you forget to fix assumptions on max features? */ in __virtio_set_bit()
184 /* Did you forget to fix assumptions on max features? */ in __virtio_clear_bit()
/linux-6.12.1/arch/powerpc/platforms/ps3/
Dsmp.c60 * Check assumptions on ps3_ipi_virqs[] indexing. If this in ps3_smp_probe()
/linux-6.12.1/arch/arm/mach-omap2/
Dwd_timer.c22 * In order to avoid any assumptions from bootloader regarding WDT
/linux-6.12.1/include/xen/interface/
Dfeatures.h92 * If neither flag is set (e.g. older Xen releases) the assumptions are:
/linux-6.12.1/drivers/usb/class/
Dcdc-acm.h30 * The only reason to have several buffers is to accommodate assumptions
/linux-6.12.1/arch/powerpc/boot/
Dgamecube-head.S13 * The entry code does no assumptions regarding:
/linux-6.12.1/arch/s390/include/asm/
Dspinlock.h31 * We make no fairness assumptions. They have a cost.
/linux-6.12.1/Documentation/devicetree/bindings/regulator/
Dpwm-regulator.yaml23 is given to the user if the assumptions made in continuous-voltage mode do
/linux-6.12.1/tools/testing/selftests/arm64/signal/testcases/
Dtestcases.h76 * Instead it makes no assumptions on the content and ordering of the
/linux-6.12.1/Documentation/infiniband/
Dcore_locking.rst5 This guide is an attempt to make explicit the locking assumptions
/linux-6.12.1/arch/arm64/lib/
Dmemcmp.S12 /* Assumptions:

12345678910