| /Linux-v4.19/arch/powerpc/kernel/ |
| D | irq.c | 102 unsigned long happened; in get_irq_happened() local
105 : "=r" (happened) : "i" (offsetof(struct paca_struct, irq_happened))); in get_irq_happened()
107 return happened; in get_irq_happened()
139 unsigned char happened = local_paca->irq_happened; in __check_irq_replay() local
161 if (happened & PACA_IRQ_HARD_DIS) { in __check_irq_replay()
169 if (!(happened & PACA_IRQ_DEC)) { in __check_irq_replay()
172 happened |= PACA_IRQ_DEC; in __check_irq_replay()
191 if (happened & PACA_IRQ_HMI) { in __check_irq_replay()
196 if (happened & PACA_IRQ_DEC) { in __check_irq_replay()
201 if (happened & PACA_IRQ_PMI) { in __check_irq_replay()
[all …]
|
| /Linux-v4.19/drivers/usb/usbip/ |
| D | usbip_event.c | 176 int happened = 0; in usbip_event_happened() local
181 happened = 1; in usbip_event_happened()
184 return happened; in usbip_event_happened()
|
| /Linux-v4.19/drivers/staging/wilc1000/ |
| D | wilc_spi.c | 921 int happened, j; in wilc_spi_read_int() local
941 happened = 0; in wilc_spi_read_int()
957 happened = 1; in wilc_spi_read_int()
961 } while (happened); in wilc_spi_read_int()
|
| /Linux-v4.19/Documentation/networking/ |
| D | xfrm_sync.txt | 149 the change happened as a result of an update.
155 happened) is set to inform the user what happened.
|
| /Linux-v4.19/arch/arm/kernel/ |
| D | hyp-stub.S | 62 strne \reg1, [\reg2, \reg3] @ record what happened and give up
|
| /Linux-v4.19/Documentation/leds/ |
| D | ledtrig-oneshot.txt | 7 happened, than the trigger turns the LED on and than keeps it off for a
|
| /Linux-v4.19/Documentation/parisc/ |
| D | debugging | 36 where exactly it happened. If you're lucky the IAOQ will point to the
|
| /Linux-v4.19/Documentation/device-mapper/ |
| D | log-writes.txt | 10 exactly as it happened originally.
51 which isn't quite what happened and wouldn't be caught during the log replay.
|
| /Linux-v4.19/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-v4.19/Documentation/admin-guide/ |
| D | bug-bisect.rst | 56 depending if the bug happened on the changeset you're testing
|
| D | bug-hunting.rst | 41 Kernel's source code where the bug happened. Depending on the severity of
181 The position where the above call happened can be seen with::
236 Once you find where the bug happened, by inspecting its location,
|
| /Linux-v4.19/Documentation/ABI/testing/ |
| D | sysfs-class-led | 41 event has happened will return an ENODATA error.
|
| /Linux-v4.19/Documentation/arm/ |
| D | kernel_user_helpers.txt | 143 Return zero if *ptr was changed or non-zero if no exchange happened.
236 changed or non-zero if no exchange happened.
|
| /Linux-v4.19/Documentation/filesystems/ext4/ondisk/ |
| 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-v4.19/Documentation/input/devices/ |
| D | rotary-encoder.rst | 68 should have happened, unless it flipped back on half the way. The
|
| /Linux-v4.19/Documentation/timers/ |
| D | timers-howto.txt | 86 that may have happened for other reasons, or at the
|
| /Linux-v4.19/fs/pstore/ |
| D | Kconfig | 115 messages, even if no oops or panic happened.
|
| /Linux-v4.19/Documentation/acpi/ |
| D | video_extension.txt | 78 it doesn't even know this happened).
|
| /Linux-v4.19/Documentation/filesystems/ |
| D | ocfs2-online-filecheck.txt | 53 1. If you want to know what error exactly happened to <inode> before fixing, do
|
| D | inotify.txt | 43 which happened first. A single queue trivially gives you ordering. Such
|
| /Linux-v4.19/arch/openrisc/ |
| D | Kconfig | 151 the last exception has happened in delay slot.
|
| /Linux-v4.19/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 what happened, and not
|
| /Linux-v4.19/Documentation/core-api/ |
| D | refcount-vs-atomic.rst | 59 counter increment or addition happened, function returned true),
|
| /Linux-v4.19/Documentation/gpu/ |
| D | introduction.rst | 77 but if your branch is not in linux-next then this must have happened by -rc6
|
| /Linux-v4.19/Documentation/usb/ |
| D | rio.txt | 28 replace it with a fresh one. In my case, what happened is I lost two 16kb
|
