| /linux-6.14.4/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-6.14.4/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-6.14.4/drivers/crypto/nx/ |
| D | nx-common-powernv.c | 263 /* these should not happen */ in wait_for_csb()
280 /* should not happen, we use physical addrs */ in wait_for_csb()
291 /* should not happen, we use physical addrs */ in wait_for_csb()
295 /* shouldn't happen, we're in HYP mode */ in wait_for_csb()
299 /* shouldn't happen, setup_ddl doesn't use many dde's */ in wait_for_csb()
304 /* shouldn't happen, we setup CRB correctly */ in wait_for_csb()
309 * shouldn't happen, setup_direct/indirect_dde creates in wait_for_csb()
315 /* shouldn't happen, setup_ddl creates DDL right */ in wait_for_csb()
319 /* shouldn't happen, setup_ddl creates DDL right */ in wait_for_csb()
323 /* should not happen with ICSWX */ in wait_for_csb()
[all …]
|
| /linux-6.14.4/Documentation/bpf/ |
| D | cpumasks.rst | 235 /* Should never happen. */
240 /* Should never happen. */
309 /* Should never happen. */
314 /* Should never happen. */
318 /* Should never happen. */
324 /* Should never happen. */
|
| /linux-6.14.4/tools/testing/selftests/kvm/x86/ |
| D | xen_shinfo_test.c | 732 "Expected event channel IRQ but it didn't happen"); in main()
745 "Expected event channel IRQ but it didn't happen"); in main()
765 "Expected event channel IRQ but it didn't happen"); in main()
776 "Expected event channel IRQ but it didn't happen"); in main()
789 "Expected event channel IRQ but it didn't happen"); in main()
800 "Expected event channel IRQ but it didn't happen"); in main()
823 "Expected event channel IRQ but it didn't happen"); in main()
837 "Expected event channel IRQ but it didn't happen"); in main()
890 "Expected event channel IRQ but it didn't happen"); in main()
907 "Expected event channel IRQ but it didn't happen"); in main()
[all …]
|
| /linux-6.14.4/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-6.14.4/drivers/md/ |
| D | dm-builtin.c | 19 * happen:
38 * being scheduled long enough, this bug may really happen.
|
| /linux-6.14.4/Documentation/networking/devlink/ |
| D | mlxsw.rst | 97 routed from a disabled router interface (RIF). This can happen during
103 routed through a disabled router interface (RIF). This can happen during
|
| /linux-6.14.4/kernel/locking/ |
| D | spinlock_debug.c | 131 * Must not happen on UP: in do_raw_spin_trylock()
171 * Must not happen on UP: in do_raw_read_trylock()
223 * Must not happen on UP: in do_raw_write_trylock()
|
| /linux-6.14.4/drivers/mtd/parsers/ |
| D | Kconfig | 37 for your particular device. It won't happen automatically. The
118 for your particular device. It won't happen automatically. The
167 for your particular device. It won't happen automatically. The
|
| /linux-6.14.4/include/uapi/linux/ |
| D | virtio_mem.h | 70 * There are no guarantees what will happen if unplugged memory is
76 * It can happen that the device cannot process a request, because it is
81 * scenarios (if the device is busy) it can happen that the device still
|
| /linux-6.14.4/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-6.14.4/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-6.14.4/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-6.14.4/arch/riscv/lib/ |
| D | delay.c | 65 * won't happen.
105 * This doesn't bother checking for overflow, as it won't happen (it's in ndelay()
|
| /linux-6.14.4/arch/um/os-Linux/ |
| D | signal.c | 280 * happen in this order, so have the barrier here. in unblock_signals()
363 * that could happen in the middle, losing the in mark_sigio_pending()
370 * timer signal (SIGALRM) cannot happen. in mark_sigio_pending()
433 * that the signal handler will either happen before or after in unblock_signals_hard()
|
| /linux-6.14.4/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-6.14.4/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-6.14.4/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-6.14.4/Documentation/userspace-api/ |
| D | mseal.rst | 12 the memory has to be marked with X bit, or else an exception will happen.
62 memory range could happen. However, those cases should be rare.
120 - mprotect, pkey_mprotect, madvise: partial update might happen, e.g.
|
| /linux-6.14.4/Documentation/mm/ |
| D | page_tables.rst | 178 happen because the CPU is trying to access memory that the current task is not
181 When these conditions happen, the MMU triggers page faults, which are types of
187 "Copy-on-Write". Page faults may also happen when frames have been swapped out
218 If the above-mentioned conditions happen in user-space, the kernel sends a
|
| /linux-6.14.4/Documentation/arch/x86/ |
| D | sgx.rst | 81 handle an EPCM fault at any time. In practice, this can happen on events like
234 When EPC page leaks happen, a WARNING like this is shown in dmesg:
285 ``EREMOVE`` happen concurrently for pages that refer to the same
286 "SECS" metadata pages. This can happen if there are concurrent
|
| /linux-6.14.4/arch/arm/include/asm/ |
| D | cti.h | 45 * the @irq happen
61 * the @irq happen
|
| /linux-6.14.4/tools/testing/selftests/drivers/net/hw/ |
| D | nic_link_layer.py | 26 #time_delay = 8 #time taken to wait for transitions to happen, in seconds.
103 …delay', type=int, default=8, help='Time taken to wait for transitions to happen(in seconds). Defau…
|
| /linux-6.14.4/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 */
|