Searched full:happening (Results 1 – 25 of 287) sorted by relevance
12345678910>>...12
| /Linux-v6.1/scripts/ |
| D | subarch.include | 2 # first, and if a usermode build is happening, the "ARCH=um" on the command
3 # line overrides the setting of ARCH below. If a native build is happening,
|
| /Linux-v6.1/Documentation/maintainer/ |
| D | messy-diffstat.rst | 13 pull request is actually doing. This document describes what is happening
59 What is happening here is that there are no longer two clear end points for
|
| /Linux-v6.1/Documentation/devicetree/bindings/i2c/ |
| D | i2c-gate.yaml | 17 no arbitration happening for gates.
|
| /Linux-v6.1/include/linux/ |
| D | task_io_accounting.h | 40 * (in its write_bytes) will not be happening. We _could_ just
|
| /Linux-v6.1/Documentation/trace/rv/ |
| D | monitor_wwnr.rst | 36 And then imagine an IRQ happening in between the lines one and two,
|
| /Linux-v6.1/lib/ |
| D | kobject_uevent.c | 450 * @kobj: struct kobject that the action is happening to
451 * @action: action that is happening
634 * @kobj: struct kobject that the action is happening to
635 * @action: action that is happening
|
| /Linux-v6.1/include/linux/platform_data/ |
| D | pm33xx.h | 18 * These flags allow PM code to exclude certain operations from happening
|
| /Linux-v6.1/include/uapi/linux/ |
| D | resource.h | 17 * structure will lose. This reduces the chances of that happening.
|
| D | eventpoll.h | 49 * from happening while those events are being processed.
|
| /Linux-v6.1/tools/testing/selftests/pidfd/ |
| D | pidfd.h | 62 * what is happening. This way we can tell the difference between a system
|
| /Linux-v6.1/drivers/misc/ibmasm/ |
| D | heartbeat.c | 27 * To prevent this from happening a callback is added the panic_notifier_list.
|
| /Linux-v6.1/arch/arm/mach-spear/ |
| D | hotplug.c | 70 * Just note it happening - when we're woken, we can report in spear13xx_do_lowpower()
|
| /Linux-v6.1/drivers/regulator/ |
| D | pwm-regulator.c | 164 * This is happening when the user needs an inversed polarity, but the in pwm_regulator_get_voltage()
200 * This is happening when the user needs an inversed polarity, but the in pwm_regulator_set_voltage()
|
| /Linux-v6.1/Documentation/admin-guide/ |
| D | md.rst | 341 fully active: IO and resync can be happening.
630 nothing is happening
633 happening. This reads all blocks and checks
638 A full check and repair is happening. This is
|
| /Linux-v6.1/Documentation/RCU/Design/Memory-Ordering/ |
| D | Tree-RCU-Memory-Ordering.rst | 63 happening before one of the above lock-release functions will be seen
64 by all CPUs as happening before any access happening after a later
66 Furthermore, any access happening before one of the
68 CPUs as happening before any access happening after a later one
|
| /Linux-v6.1/Documentation/core-api/ |
| D | index.rst | 63 How Linux keeps everything from happening at the same time. See
|
| /Linux-v6.1/arch/arm/mach-versatile/ |
| D | hotplug.c | 80 * Just note it happening - when we're woken, we can report in versatile_immitation_do_lowpower()
|
| /Linux-v6.1/arch/x86/um/ |
| D | syscalls_64.c | 26 * setting %fs may result in something else happening (like a in arch_prctl()
|
| /Linux-v6.1/drivers/clk/starfive/ |
| D | clk-starfive-jh7100.h | 102 /* protect clk enable and set rate/parent from happening at the same time */
|
| /Linux-v6.1/fs/ksmbd/ |
| D | vfs_cache.h | 98 /* if ls is happening on directory, below is valid*/
|
| /Linux-v6.1/tools/testing/selftests/net/ |
| D | reuseaddr_conflict.c | 7 * when we open the ipv6 conterpart, which is what was happening previously.
|
| /Linux-v6.1/Documentation/arm/samsung-s3c24xx/ |
| D | suspend.rst | 112 happening
|
| /Linux-v6.1/drivers/staging/media/atomisp/pci/ |
| D | atomisp-regs.h | 65 * RCOMP update is happening. The clock is gated for a minimum of 100 nsec.
|
| /Linux-v6.1/drivers/md/ |
| D | raid10.h | 9 * 2/ when resync/recovery/reshape is known to be happening - i.e. in code
|
| /Linux-v6.1/Documentation/driver-api/media/ |
| D | tx-rx.rst | 105 happening.
|
12345678910>>...12
