Home
last modified time | relevance | path

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

1234

/linux/drivers/usb/usbip/
H 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/arch/powerpc/kernel/
H A Dirq_64.c244 : happened); in arch_local_irq_restore()
257 happened: in arch_local_irq_restore()
/linux/Documentation/tools/rv/
H A Dcommon_ikm.rst11 When tracing (**-t**), also print the events that happened during the **rv**
/linux/arch/arm/kernel/
H A Dhyp-stub.S48 strne \reg1, [\reg2] @ record what happened and give up
/linux/Documentation/leds/
H A Dledtrig-oneshot.rst8 happened, then the trigger turns the LED on and then keeps it off for a
/linux/Documentation/arch/parisc/
H A Ddebugging.rst43 where exactly it happened. If you're lucky the IAOQ will point to the
/linux/Documentation/admin-guide/device-mapper/
H 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/Documentation/driver-api/usb/
H 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/Documentation/arch/arm/
H 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/Documentation/admin-guide/
H A Dfilesystem-monitoring.rst16 for a monitoring tool to know a problem in the file system has happened.
H 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
/linux/Documentation/ABI/testing/
H A Dsysfs-class-led60 event has happened will return an ENODATA error.
/linux/Documentation/input/devices/
H A Drotary-encoder.rst68 should have happened, unless it flipped back on half the way. The
/linux/Documentation/firmware-guide/acpi/
H A Dvideo_extension.rst89 it doesn't even know this happened).
/linux/Documentation/input/joydev/
H A Djoystick-api.rst146 presses happened at the same time, and similar.
191 The other reason is that you want to know all that happened, and not
/linux/tools/memory-model/Documentation/
H A Dordering.txt70 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/Documentation/filesystems/
H A Dinotify.rst52 which happened first. A single queue trivially gives you ordering. Such
/linux/Documentation/maintainer/
H A Dmessy-diffstat.rst66 may be impossible to tell what actually happened in the changes leading up
/linux/Documentation/arch/x86/
H A Dexception-tables.rst189 file. But first we want to find out what happened to our code in the
232 What happened? The assembly directives::
H A Damd_hsmp.rst184 what happened. The transaction returns 0 on success.
/linux/arch/arc/kernel/
H A Dentry-compact.S356 ; paranoid check, given A1 was active when A2 happened, preempt count
/linux/Documentation/admin-guide/laptops/
H A Dsony-laptop.rst166 happened to me, this driver could do very bad things to your
/linux/Documentation/process/
H A Dbackporting.rst99 For backports, what likely happened was that the branch you are
142 development could have happened on either branch, or the branches have
292 3-way combined diffs include all the other changes that happened to the
465 to be adjusted. ``git log`` is your friend to figure out what happened
/linux/fs/pstore/
H A DKconfig42 messages, even if no oops or panic happened.
/linux/arch/openrisc/
H A DKconfig215 the last exception has happened in delay slot.

1234