Home
last modified time | relevance | path

Searched full:happen (Results 1 – 25 of 2447) sorted by relevance

12345678910>>...98

/kernel/linux/linux-5.10/Documentation/crypto/
Ddevel-algos.rst72 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 -----------
/kernel/linux/linux-5.10/arch/arm/mach-omap2/
Dpowerdomain-common.c61 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()
/kernel/linux/linux-5.10/drivers/crypto/nx/
Dnx-common-powernv.c266 /* 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 …]
/kernel/linux/linux-5.10/drivers/oprofile/
Devent_buffer.c47 * This shouldn't happen since all workqueues or handlers are in add_event_entry()
175 /* can't currently happen */ in event_buffer_read()
181 /* May happen if the buffer is freed during pending reads. */ in event_buffer_read()
/kernel/linux/linux-5.10/drivers/mtd/parsers/
DKconfig32 for your particular device. It won't happen automatically. The
94 for your particular device. It won't happen automatically. The
128 for your particular device. It won't happen automatically. The
/kernel/linux/linux-5.10/drivers/md/
Ddm-builtin.c19 * happen:
38 * being scheduled long enough, this bug may really happen.
/kernel/linux/linux-5.10/Documentation/networking/devlink/
Dmlxsw.rst73 routed from a disabled router interface (RIF). This can happen during
79 routed through a disabled router interface (RIF). This can happen during
/kernel/linux/linux-5.10/Documentation/core-api/
Dunaligned-memory-access.rst28 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.
/kernel/linux/linux-5.10/include/linux/sched/
Dwake_q.h19 * 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
/kernel/linux/linux-5.10/kernel/locking/
Dspinlock_debug.c128 * Must not happen on UP: in do_raw_spin_trylock()
167 * Must not happen on UP: in do_raw_read_trylock()
219 * Must not happen on UP: in do_raw_write_trylock()
/kernel/linux/linux-5.10/include/uapi/linux/
Dvirtio_mem.h70 * 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
/kernel/linux/linux-5.10/fs/xfs/libxfs/
Dxfs_defer.h27 * whatever action had to happen to the extent list and file the log done
95 * This doesn't normally happen except log recovery.
/kernel/linux/linux-5.10/fs/reiserfs/
Dlock.c57 /* 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()
/kernel/linux/linux-5.10/arch/c6x/lib/
Dremu.S47 ;; RETURN A may happen here (note: must happen before the next branch)
Ddivremu.S45 ;; RETURN A may happen here (note: must happen before the next branch)
Ddivu.S57 ;; RETURN A may happen here (note: must happen before the next branch)
/kernel/linux/linux-5.10/arch/sh/drivers/pci/
Dops-dreamcast.c21 * The !gapspci_config_access case really shouldn't happen, ever, unless
34 * likely to happen anytime soon.
/kernel/linux/linux-5.10/arch/riscv/lib/
Ddelay.c61 * won't happen.
101 * This doesn't bother checking for overflow, as it won't happen (it's in ndelay()
/kernel/linux/linux-5.10/tools/testing/selftests/ptrace/
Dget_syscall_info.c90 /* cannot happen */ in TEST()
128 /* cannot happen */ in TEST()
142 /* cannot happen */ in TEST()
/kernel/linux/linux-5.10/drivers/block/paride/
DTransition-notes4 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
/kernel/linux/linux-5.10/Documentation/ABI/testing/
Dsysfs-bus-rpmsg28 wasn't assigned (can happen if no driver exists for this
46 wasn't assigned (can happen if the kernel driver that
/kernel/linux/linux-5.10/arch/arm/include/asm/
Dcti.h45 * the @irq happen
61 * the @irq happen
/kernel/linux/linux-5.10/net/x25/
Dx25_forward.c32 /* This shouldn't happen, if it occurs somehow in x25_forward_call()
46 * established LCI? It shouldn't happen, just in case.. in x25_forward_call()
/kernel/linux/linux-5.10/drivers/staging/kpc2000/
DTODO1 …oesn't seem to let multiple transactions (to different instances of the core) happen in parallel...
/kernel/linux/linux-5.10/kernel/
Dextable.c131 * 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()

12345678910>>...98