Searched refs:happened (Results 1 – 25 of 106) sorted by relevance
12345
| /linux-6.12.1/drivers/usb/usbip/ |
| D | usbip_event.c | 177 int happened = 0; in usbip_event_happened() local
182 happened = 1; in usbip_event_happened()
185 return happened; in usbip_event_happened()
|
| /linux-6.12.1/arch/powerpc/kernel/ |
| D | irq_64.c | 244 : happened); in arch_local_irq_restore()
257 happened: in arch_local_irq_restore()
|
| /linux-6.12.1/Documentation/tools/rv/ |
| D | common_ikm.rst | 11 When tracing (**-t**), also print the events that happened during the **rv**
|
| /linux-6.12.1/arch/arm/kernel/ |
| D | hyp-stub.S | 48 strne \reg1, [\reg2] @ record what happened and give up
|
| /linux-6.12.1/Documentation/networking/ |
| D | xfrm_sync.rst | 168 the change happened as a result of an update.
175 happened) is set to inform the user what happened.
|
| /linux-6.12.1/Documentation/leds/ |
| D | ledtrig-oneshot.rst | 8 happened, then the trigger turns the LED on and then keeps it off for a
|
| /linux-6.12.1/Documentation/filesystems/ext4/ |
| D | super.rst | 363 - First time an error happened, in seconds since the epoch.
375 - Name of function where the error happened.
379 - Line number where error happened.
391 - Line number where most recent error happened.
399 - Name of function where the most recent error happened.
|
| /linux-6.12.1/Documentation/driver-api/usb/ |
| D | persist.rst | 22 has no way to know what has actually happened. Perhaps the same
60 has happened; look for lines saying "root hub lost power or was reset".
157 happened and will continue to use the partition tables, inodes, and
|
| /linux-6.12.1/Documentation/admin-guide/device-mapper/ |
| D | log-writes.rst | 11 exactly as it happened originally.
52 which isn't quite what happened and wouldn't be caught during the log replay.
|
| /linux-6.12.1/Documentation/arch/parisc/ |
| D | debugging.rst | 43 where exactly it happened. If you're lucky the IAOQ will point to the
|
| /linux-6.12.1/Documentation/arch/arm/ |
| D | kernel_user_helpers.rst | 144 Return zero if `*ptr` was changed or non-zero if no exchange happened.
237 changed or non-zero if no exchange happened.
|
| /linux-6.12.1/Documentation/ABI/testing/ |
| D | sysfs-class-led | 60 event has happened will return an ENODATA error.
|
| /linux-6.12.1/Documentation/trace/ |
| D | debugging.rst | 60 use kexec/kdump. But these just show what happened at the time of the crash.
61 It can be very useful in knowing what happened up to the point of the crash.
|
| /linux-6.12.1/Documentation/admin-guide/ |
| D | filesystem-monitoring.rst | 16 for a monitoring tool to know a problem in the file system has happened.
|
| D | perf-security.rst | 240 monitoring. CPU and system events happened when executing either in
249 happened when executing either in user or in kernel space can be
256 system events happened when executing in user space only can be
|
| D | bug-hunting.rst | 41 Kernel's source code where the bug happened. Depending on the severity of
185 The position where the above call happened can be seen with::
244 Once you find where the bug happened, by inspecting its location,
|
| /linux-6.12.1/Documentation/arch/x86/ |
| D | amd_hsmp.rst | 97 what happened. The transaction returns 0 on success.
|
| /linux-6.12.1/Documentation/input/devices/ |
| D | rotary-encoder.rst | 68 should have happened, unless it flipped back on half the way. The
|
| /linux-6.12.1/Documentation/networking/devlink/ |
| D | devlink-health.rst | 11 order to know when something bad happened to a PCI device.
|
| /linux-6.12.1/tools/memory-model/Documentation/ |
| D | ordering.txt | 70 by that CPU happened before any later action taken by that same CPU.
77 All CPUs will agree that the store to "x" happened before the load
97 All CPUs will agree that any operation in a given partition happened
183 Then any given CPU will see the write to "x" has having happened before
|
| /linux-6.12.1/Documentation/input/joydev/ |
| D | joystick-api.rst | 146 presses happened at the same time, and similar.
191 The other reason is that you want to know all that happened, and not
|
| /linux-6.12.1/Documentation/filesystems/ |
| D | ocfs2-online-filecheck.rst | 56 1. If you want to know what error exactly happened to <inode> before fixing, do::
|
| D | inotify.rst | 52 which happened first. A single queue trivially gives you ordering. Such
|
| /linux-6.12.1/Documentation/firmware-guide/acpi/ |
| D | video_extension.rst | 89 it doesn't even know this happened).
|
| /linux-6.12.1/Documentation/timers/ |
| D | timers-howto.rst | 93 that may have happened for other reasons, or at the
|
12345