Home
last modified time | relevance | path

Searched full:impossible (Results 1 – 25 of 497) sorted by relevance

12345678910>>...20

/linux-5.10/Documentation/power/
Duserland-swsusp.rst27 reading and writing. It is also impossible to have the device open more than
67 this number, but if it turns out to be impossible, the kernel will
122 - read()s across page boundaries are impossible (ie. if you read() 1/2 of
/linux-5.10/arch/sparc/kernel/
Dunaligned_32.c59 printk("Impossible unaligned trap. insn=%08x\n", insn); in decode_access_size()
267 panic("Impossible kernel unaligned trap."); in kernel_unaligned_trap()
362 unaligned_panic("Impossible user unaligned trap."); in user_unaligned_trap()
/linux-5.10/drivers/media/platform/omap/
Domap_voutlib.c61 * impossible and cannot reasonably be adjusted.
113 * impossible and cannot reasonably be adjusted.
167 * impossible and cannot reasonably be adjusted.
/linux-5.10/drivers/net/wireless/ath/wil6210/
DKconfig30 such monitoring impossible.
/linux-5.10/arch/mips/mm/
Dtlb-r4k.c61 /* Save old context and create impossible VPN2 value */ in local_flush_tlb_all()
396 /* Save old context and create impossible VPN2 value */ in add_wired_entry()
463 /* Save old context and create impossible VPN2 value */ in add_temporary_entry()
/linux-5.10/arch/arm/lib/
Dcsumpartialcopyuser.S76 * We report fault by returning 0 csum - impossible in normal case, since
/linux-5.10/Documentation/ABI/testing/
Dconfigfs-usb-gadget-mass-storage27 is enabled as well as when it was impossible
/linux-5.10/arch/um/drivers/
Dstderr_console.c49 * impossible to open. My FC5 filesystem started having init die, and the
/linux-5.10/fs/bfs/
Dbfs.h15 if a filesystem is mounted with such "impossible to fill up" number of inodes */
/linux-5.10/Documentation/process/
Ddeprecated.rst34 Use WARN() and WARN_ON() instead, and handle the "impossible"
36 of APIs were originally designed to act as an "impossible situation"
40 destabilize a system or entirely break it, which makes it impossible
/linux-5.10/Documentation/PCI/
Dpciebus-howto.rst52 Port. In other words, it is impossible to have multiple service
90 impossible to load any service driver once the kernel has loaded the
/linux-5.10/arch/arm/kernel/
Dhibernate.c97 * and that would make function calls impossible; switch to a temporary
/linux-5.10/kernel/time/
Djiffies.c17 * this would make NTP adjustments impossible as they are
/linux-5.10/kernel/sched/
Dstop_task.c96 BUG(); /* its impossible to change to this class */ in switched_to_stop()
/linux-5.10/Documentation/filesystems/
Dvirtiofs.rst74 impossible to add high priority requests. In order to address this difference,
/linux-5.10/Documentation/devicetree/bindings/timer/
Darm,arch_timer_mmio.yaml41 strongly discouraged; fix your firmware unless absolutely impossible.
Darm,arch_timer.yaml47 strongly discouraged; fix your firmware unless absolutely impossible.
/linux-5.10/Documentation/hwmon/
Dpcf8591.rst68 The PCF8591 is plainly impossible to detect! Thus the driver won't even
Dpmbus-core.rst48 many variables to consider. For example, it is almost impossible to autodetect
323 register is impossible, and the PMBUS_SKIP_STATUS_CHECK flag must be set.
/linux-5.10/Documentation/driver-api/soundwire/
Derror_handling.rst48 Slave device and are likely impossible to recover from.
/linux-5.10/arch/x86/entry/vsyscall/
Dvsyscall_64.c18 * - The whole concept is impossible for 32-bit compat userspace.
274 * generate one here. (This should be impossible.) in emulate_vsyscall()
/linux-5.10/Documentation/gpu/
Ddrm-uapi.rst54 and flexible, and therefore it is almost always impossible to precisely define
61 becomes impossible to change the implementation details, since userspace could
64 much impossible. As a consequence this means:
/linux-5.10/include/linux/
Dhmm.h29 * HMM_PFN_ERROR - accessing the pfn is impossible and the device should
/linux-5.10/drivers/gpu/drm/amd/amdgpu/
Damdgpu_sched.c158 /* Impossible. in amdgpu_sched_ioctl()
/linux-5.10/Documentation/networking/device_drivers/ethernet/3com/
D3c509.rst143 or impossible in normal operation. Possible causes of this error report are:
212 0x04 Status stack overflow (normally impossible).

12345678910>>...20