Searched full:happen (Results 1 – 25 of 241) sorted by relevance
12345678910
| /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 -----------
|
| /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
|
| /Documentation/devicetree/bindings/net/wireless/ |
| D | ieee80211.txt | 9 normally. It may happen chipset supports a wide wireless band but it is
|
| /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.
|
| /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
|
| /Documentation/i2c/busses/ |
| D | i2c-via.rst | 38 This can happen. This driver uses the pins VIA recommends in their
|
| /Documentation/devicetree/bindings/leds/backlight/ |
| D | common.yaml | 31 on the brightness apart from what the driver says, as it could happen
|
| /Documentation/block/ |
| D | switching-sched.rst | 25 device name (hda, hdb, sga, or whatever you happen to have).
|
| /Documentation/x86/ |
| D | usb-legacy-support.rst | 27 3) If AMD64 64-bit mode is enabled, again system crashes often happen,
|
| /Documentation/vm/ |
| D | hwpoison.rst | 27 when that happens another machine check will happen.
31 users, because memory failures could happen anytime and anywhere,
|
| /Documentation/userspace-api/media/dvb/ |
| D | dmx-fwrite.rst | 58 - No data was written. This might happen if ``O_NONBLOCK`` was
|
| /Documentation/maintainer/ |
| D | configure-git.rst | 50 This can be configured to happen automatically any time you issue ``git am``
|
| /Documentation/userspace-api/media/ |
| D | gen-errors.rst | 23 can't perform it. This could happen for example in case where
|
| /Documentation/ |
| D | atomic_t.txt | 110 In this case we would expect the atomic_set() from CPU1 to either happen
258 This should not happen; but a hypothetical atomic_inc_acquire() --
|
| D | asm-annotations.rst | 78 the function can happen in a standard way. When frame pointers are enabled,
79 save/restore of frame pointer shall happen at the start/end of a function,
|
| /Documentation/scheduler/ |
| D | completion.rst | 43 Note that while initialization must happen first, the waiting and signaling
44 part can happen in any order. I.e. it's entirely normal for a thread
80 does not happen until all related activities (complete() or reinit_completion())
|
| /Documentation/RCU/ |
| D | stallwarn.rst | 48 happen to preempt a low-priority task in the middle of an RCU
228 handlers are no longer able to execute on this CPU. This can happen if
260 This is rare, but does happen from time to time in real life. It is also
262 on how the stall warning and the grace-period initialization happen to
|
| D | rcu_dereference.rst | 56 and "b" are integers that happen to be equal, the expression
106 can now be speculated, such that it might happen before the
160 bugs more likely to happen. Which can be a good thing,
161 at least if they happen during testing. An example
|
| /Documentation/misc-devices/ |
| D | apds990x.rst | 24 (infrared + visible light) and IR only. However, threshold comparisons happen
|
| /Documentation/driver-api/soundwire/ |
| D | error_handling.rst | 6 be very unlikely, and if they happen it should be limited to single bit
|
| /Documentation/security/ |
| D | sak.rst | 26 happen.
|
| /Documentation/userspace-api/media/mediactl/ |
| D | media-ioc-g-topology.rst | 37 return, if no errors happen, this ioctl will return the
291 may happen if the ``topology_version`` changed when compared to the
|
| /Documentation/usb/ |
| D | raw-gadget.rst | 70 like all USB request processing happen during the lifetime of a syscall),
|
| /Documentation/w1/masters/ |
| D | ds2490.rst | 58 not happen.
|
| /Documentation/x86/x86_64/ |
| D | machinecheck.rst | 53 Since machine check exceptions can happen any time it is sometimes
|
12345678910