Home
last modified time | relevance | path

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

1234567

/OK3568_Linux_fs/kernel/arch/powerpc/kernel/
H A Dirq.c97 unsigned long happened; in get_irq_happened() local
100 : "=r" (happened) : "i" (offsetof(struct paca_struct, irq_happened))); in get_irq_happened()
102 return happened; in get_irq_happened()
128 unsigned char happened = local_paca->irq_happened; in __check_irq_replay() local
137 if (happened & PACA_IRQ_DEC) { in __check_irq_replay()
142 if (happened & PACA_IRQ_EE) { in __check_irq_replay()
147 if (happened & PACA_IRQ_DBELL) { in __check_irq_replay()
152 if (happened & PACA_IRQ_HARD_DIS) in __check_irq_replay()
/OK3568_Linux_fs/kernel/drivers/usb/usbip/
H A Dusbip_event.c178 int happened = 0; in usbip_event_happened() local
183 happened = 1; in usbip_event_happened()
186 return happened; in usbip_event_happened()
/OK3568_Linux_fs/yocto/poky/meta/recipes-kernel/linux-libc-headers/linux-libc-headers/
H A D0001-scripts-Use-fixed-input-and-output-files-instead-of-.patch21 One observed case happened in docker where the /tmp could be so rarely used that
36 information in case something else wrong happened.
/OK3568_Linux_fs/yocto/meta-openembedded/meta-python/recipes-devtools/python/
H A Dpython3-trafaret-config_2.0.2.bb1 …checks config using trafaret while keeping track of actual lines of file where error has happened."
/OK3568_Linux_fs/yocto/meta-openembedded/meta-oe/recipes-devtools/uw-imap/uw-imap/
H A Dimap-2007f-format-security.patch15 mm_log (tmp,WARN); /* give the user a warning of what happened */
/OK3568_Linux_fs/kernel/Documentation/networking/
H A Dxfrm_sync.rst168 the change happened as a result of an update.
175 happened) is set to inform the user what happened.
/OK3568_Linux_fs/kernel/arch/arm/kernel/
H A Dhyp-stub.S49 strne \reg1, [\reg2, \reg3] @ record what happened and give up
/OK3568_Linux_fs/buildroot/package/norm/
H A D0001-protolib-drop-linux-version-check.patch1 The char * to unsigned char * change happened for the libnetfilter_queue
/OK3568_Linux_fs/buildroot/dl/qt5location/git/dist/
H A Dchanges-5.3.231 This happened when using static builds of Qt (e.g. on iOS) and the
/OK3568_Linux_fs/kernel/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
/OK3568_Linux_fs/kernel/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.
/OK3568_Linux_fs/kernel/Documentation/leds/
H A Dledtrig-oneshot.rst8 happened, than the trigger turns the LED on and than keeps it off for a
/OK3568_Linux_fs/yocto/poky/meta/recipes-multimedia/libomxil/libomxil-0.9.3/
H A Dconfigure-fix.patch3 For example, at least the following errors happened to some compilers:
/OK3568_Linux_fs/kernel/Documentation/parisc/
H A Ddebugging.rst43 where exactly it happened. If you're lucky the IAOQ will point to the
/OK3568_Linux_fs/kernel/Documentation/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.
/OK3568_Linux_fs/kernel/Documentation/admin-guide/
H A Dbug-bisect.rst56 depending if the bug happened on the changeset you're testing
H A Dperf-security.rst183 monitoring. CPU and system events happened when executing either in
192 happened when executing either in user or in kernel space can be
199 system events happened when executing in user space only can be
H 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,
/OK3568_Linux_fs/kernel/Documentation/filesystems/ext4/
H 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.
/OK3568_Linux_fs/yocto/poky/meta/recipes-devtools/automake/automake/
H A Dperformance.patch46 - # happened. Such a system could not be considered "sane".
/OK3568_Linux_fs/kernel/tools/lib/traceevent/Documentation/
H A Dlibtraceevent-handle.txt63 /* Something wrong happened, the counter is not incremented by 1 */
/OK3568_Linux_fs/kernel/Documentation/ABI/testing/
H A Dsysfs-class-led60 event has happened will return an ENODATA error.
/OK3568_Linux_fs/kernel/Documentation/networking/devlink/
H A Ddevlink-health.rst11 order to know when something bad happened to a PCI device.
/OK3568_Linux_fs/yocto/meta-openembedded/meta-networking/recipes-netkit/netkit-telnet/files/
H A D0001-telnet-telnetd-Fix-deadlock-on-cleanup.patch29 and what has happened here is that the user closes the telnet session
/OK3568_Linux_fs/kernel/Documentation/input/devices/
H A Drotary-encoder.rst68 should have happened, unless it flipped back on half the way. The

1234567