| /Linux-v5.15/Documentation/crypto/ |
| D | devel-algos.rst | 72 other part of the kernel. Note that the .cia_setkey() call might happen
73 before or after any of these schematics happen, but must not happen
172 other part of the kernel. Note that the .setkey() call might happen
173 before or after any of these schematics happen, but must not happen
210 ----------- other transformations happen here -----------
|
| /Linux-v5.15/arch/arm/mach-omap2/ |
| D | powerdomain-common.c | 61 WARN_ON(1); /* should never happen */ in omap2_pwrdm_get_mem_bank_onstate_mask()
81 WARN_ON(1); /* should never happen */ in omap2_pwrdm_get_mem_bank_retst_mask()
101 WARN_ON(1); /* should never happen */ in omap2_pwrdm_get_mem_bank_stst_mask()
|
| /Linux-v5.15/drivers/crypto/nx/ |
| D | nx-common-powernv.c | 266 /* these should not happen */ in wait_for_csb()
283 /* should not happen, we use physical addrs */ in wait_for_csb()
294 /* should not happen, we use physical addrs */ in wait_for_csb()
298 /* shouldn't happen, we're in HYP mode */ in wait_for_csb()
302 /* shouldn't happen, setup_ddl doesn't use many dde's */ in wait_for_csb()
307 /* shouldn't happen, we setup CRB correctly */ in wait_for_csb()
312 * shouldn't happen, setup_direct/indirect_dde creates in wait_for_csb()
318 /* shouldn't happen, setup_ddl creates DDL right */ in wait_for_csb()
322 /* shouldn't happen, setup_ddl creates DDL right */ in wait_for_csb()
326 /* should not happen with ICSWX */ in wait_for_csb()
[all …]
|
| /Linux-v5.15/Documentation/core-api/ |
| D | unaligned-memory-access.rst | 28 The above may seem a little vague, as memory access can happen in different
62 happen. The exception handler is able to correct the unaligned access,
65 happen, but the exceptions do not contain enough information for the
72 memory accesses to happen, your code will not work correctly on certain
172 Think about what would happen if addr1 was an odd address such as 0x10003.
|
| /Linux-v5.15/drivers/mtd/parsers/ |
| D | Kconfig | 32 for your particular device. It won't happen automatically. The
113 for your particular device. It won't happen automatically. The
147 for your particular device. It won't happen automatically. The
|
| /Linux-v5.15/drivers/md/ |
| D | dm-builtin.c | 19 * happen:
38 * being scheduled long enough, this bug may really happen.
|
| /Linux-v5.15/Documentation/networking/devlink/ |
| D | mlxsw.rst | 73 routed from a disabled router interface (RIF). This can happen during
79 routed through a disabled router interface (RIF). This can happen during
|
| /Linux-v5.15/include/linux/sched/ |
| D | wake_q.h | 19 * already in a wake queue, the wakeup will happen soon and the second
31 * NOTE that there is no guarantee the wakeup will happen any later than the
|
| /Linux-v5.15/kernel/locking/ |
| D | spinlock_debug.c | 130 * Must not happen on UP: in do_raw_spin_trylock()
170 * Must not happen on UP: in do_raw_read_trylock()
222 * Must not happen on UP: in do_raw_write_trylock()
|
| /Linux-v5.15/include/uapi/linux/ |
| D | virtio_mem.h | 70 * There are no guarantees what will happen if unplugged memory is
75 * It can happen that the device cannot process a request, because it is
80 * scenarios (if the device is busy) it can happen that the device still
|
| /Linux-v5.15/arch/riscv/lib/ |
| D | delay.c | 61 * won't happen.
101 * This doesn't bother checking for overflow, as it won't happen (it's in ndelay()
|
| /Linux-v5.15/arch/sh/drivers/pci/ |
| D | ops-dreamcast.c | 21 * The !gapspci_config_access case really shouldn't happen, ever, unless
34 * likely to happen anytime soon.
|
| /Linux-v5.15/fs/reiserfs/ |
| D | lock.c | 57 /* this can happen when the lock isn't always held */ in reiserfs_write_unlock_nested()
74 /* this can happen when the lock isn't always held */ in reiserfs_write_lock_nested()
|
| /Linux-v5.15/fs/xfs/libxfs/ |
| D | xfs_defer.h | 27 * whatever action had to happen to the extent list and file the log done
95 * This doesn't normally happen except log recovery.
|
| /Linux-v5.15/Documentation/RCU/ |
| D | stallwarn.rst | 48 happen to preempt a low-priority task in the middle of an RCU
96 the ``rcu_.*timer wakeup didn't happen for`` console-log message,
232 handlers are no longer able to execute on this CPU. This can happen if
264 This is rare, but does happen from time to time in real life. It is also
266 on how the stall warning and the grace-period initialization happen to
303 kthread timer wakeup didn't happen for 23804 jiffies! g7076 f0x0 RCU_GP_WAIT_FQS(5) ->state=0x402
|
| /Linux-v5.15/drivers/block/paride/ |
| D | Transition-notes | 4 Proof: All assignments to ps_tq_active and all scheduling of ps_tq happen
5 under ps_spinlock. There are three places where that can happen:
74 from pd.c. That could happen only if pi_do_claimed() had been
|
| /Linux-v5.15/tools/testing/selftests/ptrace/ |
| D | get_syscall_info.c | 90 /* cannot happen */ in TEST()
128 /* cannot happen */ in TEST()
142 /* cannot happen */ in TEST()
|
| /Linux-v5.15/Documentation/ABI/testing/ |
| D | sysfs-bus-rpmsg | 28 wasn't assigned (can happen if no driver exists for this
46 wasn't assigned (can happen if the kernel driver that
|
| /Linux-v5.15/drivers/scsi/elx/libefc/ |
| D | efc_domain.c | 443 /* Should not happen */ in __efc_domain_wait_alloc()
502 /* Should not happen */ in __efc_domain_allocated()
503 efc_log_err(efc, "%s: evt: %d should not happen\n", in __efc_domain_allocated()
598 /* Should not happen */ in __efc_domain_wait_attach()
599 efc_log_err(efc, "%s: evt: %d should not happen\n", in __efc_domain_wait_attach()
667 /* Should not happen */ in __efc_domain_ready()
668 efc_log_err(efc, "%s: evt: %d should not happen\n", in __efc_domain_ready()
673 /* can happen during p2p */ in __efc_domain_ready()
|
| /Linux-v5.15/drivers/block/zram/ |
| D | zram_drv.h | 75 atomic64_t failed_reads; /* can happen when memory is too low */
76 atomic64_t failed_writes; /* can happen when memory is too low */
|
| /Linux-v5.15/net/x25/ |
| D | x25_forward.c | 31 /* This shouldn't happen, if it occurs somehow in x25_forward_call()
45 * established LCI? It shouldn't happen, just in case.. in x25_forward_call()
|
| /Linux-v5.15/arch/arm/include/asm/ |
| D | cti.h | 45 * the @irq happen
61 * the @irq happen
|
| /Linux-v5.15/kernel/ |
| D | extable.c | 131 * watching again. This can happen either by tracing that in kernel_text_address()
141 /* Treat this like an NMI as it can happen anywhere */ in kernel_text_address()
|
| /Linux-v5.15/drivers/hid/ |
| D | hid-mf.c | 79 hid_err(hid, "Invalid report, this should never happen!\n"); in mf_init()
84 hid_err(hid, "Missing input, this should never happen!\n"); in mf_init()
|
| /Linux-v5.15/arch/arm/kernel/ |
| D | machine_kexec.c | 158 * This can only happen if machine_shutdown() failed to disable some in machine_kexec()
159 * CPU, and that can only happen if the checks in in machine_kexec()
|
