Home
last modified time | relevance | path

Searched refs:happened (Results 1 – 25 of 104) sorted by relevance

12345

/linux-6.3-rc2/drivers/usb/usbip/
A Dusbip_event.c177 int happened = 0; in usbip_event_happened() local
182 happened = 1; in usbip_event_happened()
185 return happened; in usbip_event_happened()
/linux-6.3-rc2/arch/powerpc/kernel/
A Dirq_64.c244 : happened); in arch_local_irq_restore()
257 happened: in arch_local_irq_restore()
/linux-6.3-rc2/Documentation/tools/rv/
A Dcommon_ikm.rst11 When tracing (**-t**), also print the events that happened during the **rv**
/linux-6.3-rc2/arch/arm/kernel/
A Dhyp-stub.S48 strne \reg1, [\reg2] @ record what happened and give up
/linux-6.3-rc2/Documentation/networking/
A Dxfrm_sync.rst168 the change happened as a result of an update.
175 happened) is set to inform the user what happened.
/linux-6.3-rc2/Documentation/leds/
A Dledtrig-oneshot.rst8 happened, than the trigger turns the LED on and than keeps it off for a
/linux-6.3-rc2/Documentation/devicetree/bindings/iio/proximity/
A Dsemtech,sx9360.yaml26 and data is available or that a close/far proximity event has happened.
A Dsemtech,sx9310.yaml31 available or that a close/far proximity event has happened.
A Dsemtech,sx9324.yaml26 and data is available or that a close/far proximity event has happened.
/linux-6.3-rc2/Documentation/parisc/
A Ddebugging.rst43 where exactly it happened. If you're lucky the IAOQ will point to the
/linux-6.3-rc2/Documentation/admin-guide/device-mapper/
A Dlog-writes.rst11 exactly as it happened originally.
52 which isn't quite what happened and wouldn't be caught during the log replay.
/linux-6.3-rc2/Documentation/driver-api/usb/
A Dpersist.rst22 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.3-rc2/Documentation/filesystems/ext4/
A Dsuper.rst363 - 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.3-rc2/Documentation/admin-guide/
A Dbug-bisect.rst56 depending if the bug happened on the changeset you're testing
A Dfilesystem-monitoring.rst16 for a monitoring tool to know a problem in the file system has happened.
A Dperf-security.rst240 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
A Dbug-hunting.rst41 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.3-rc2/Documentation/arm/
A Dkernel_user_helpers.rst144 Return zero if `*ptr` was changed or non-zero if no exchange happened.
237 changed or non-zero if no exchange happened.
/linux-6.3-rc2/Documentation/ABI/testing/
A Dsysfs-class-led60 event has happened will return an ENODATA error.
/linux-6.3-rc2/Documentation/x86/
A Damd_hsmp.rst78 what happened. The transaction returns 0 on success.
/linux-6.3-rc2/Documentation/input/devices/
A Drotary-encoder.rst68 should have happened, unless it flipped back on half the way. The
/linux-6.3-rc2/Documentation/networking/devlink/
A Ddevlink-health.rst11 order to know when something bad happened to a PCI device.
/linux-6.3-rc2/Documentation/timers/
A Dtimers-howto.rst93 that may have happened for other reasons, or at the
/linux-6.3-rc2/Documentation/filesystems/
A Docfs2-online-filecheck.rst56 1. If you want to know what error exactly happened to <inode> before fixing, do::
/linux-6.3-rc2/Documentation/firmware-guide/acpi/
A Dvideo_extension.rst89 it doesn't even know this happened).

Completed in 27 milliseconds

12345