Home
last modified time | relevance | path

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

123

/linux-3.4.99/arch/powerpc/kernel/
Dirq.c100 unsigned long happened; in get_irq_happened() local
103 : "=r" (happened) : "i" (offsetof(struct paca_struct, irq_happened))); in get_irq_happened()
105 return happened; in get_irq_happened()
145 unsigned char happened = local_paca->irq_happened; in __check_irq_replay() local
165 if ((happened & PACA_IRQ_DEC) || decrementer_check_overflow()) in __check_irq_replay()
170 if (happened & PACA_IRQ_EE) in __check_irq_replay()
179 if (happened & PACA_IRQ_EE_EDGE) in __check_irq_replay()
183 if (happened & PACA_IRQ_DBELL) in __check_irq_replay()
/linux-3.4.99/drivers/staging/usbip/
Dusbip_event.c117 int happened = 0; in usbip_event_happened() local
121 happened = 1; in usbip_event_happened()
124 return happened; in usbip_event_happened()
Dusbip_protocol.txt300 | | | otherwise some kind of error happened.
/linux-3.4.99/Documentation/networking/
Dxfrm_sync.txt149 the change happened as a result of an update.
155 happened) is set to inform the user what happened.
/linux-3.4.99/drivers/staging/wlags49_h2/
DTODO4 Since this will not happen by magic and has not happened until now this
/linux-3.4.99/drivers/staging/wlags49_h25/
DTODO4 Since this will not happen by magic and has not happened until now this
/linux-3.4.99/Documentation/parisc/
Ddebugging36 where exactly it happened. If you're lucky the IAOQ will point to the
/linux-3.4.99/Documentation/usb/
Dpersist.txt19 has no way to know what has actually happened. Perhaps the same
57 has happened; look for lines saying "root hub lost power or was reset".
151 happened and will continue to use the partition tables, inodes, and
Drio.txt28 replace it with a fresh one. In my case, what happened is I lost two 16kb
/linux-3.4.99/arch/frv/kernel/
Dbreak.S321 # return to where the interrupt happened
356 # return to where the trap happened
/linux-3.4.99/Documentation/arm/
Dkernel_user_helpers.txt143 Return zero if *ptr was changed or non-zero if no exchange happened.
236 changed or non-zero if no exchange happened.
/linux-3.4.99/arch/openrisc/
DKconfig121 the last exception has happened in delay slot.
/linux-3.4.99/Documentation/timers/
Dtimers-howto.txt86 that may have happened for other reasons, or at the
/linux-3.4.99/Documentation/input/
Drotary-encoder.txt61 should have happened, unless it flipped back on half the way. The
Djoystick-api.txt118 presses happened at the same time, and similar.
161 The other reason is that you want to know all what happened, and not
/linux-3.4.99/Documentation/frv/
Dkernel-ABI.txt174 another flag and resume execution at the point the interrupt happened.
216 determines that the interrupt shouldn't actually have happened. It
/linux-3.4.99/Documentation/x86/
Dexception-tables.txt183 file. But first we want to find out what happened to our code in the
225 What happened? The assembly directives
/linux-3.4.99/arch/mips/
DKconfig.debug76 provides another way to check stack overflow happened on kernel mode
/linux-3.4.99/Documentation/scheduler/
Dsched-domains.txt35 at the time the scheduler_tick() happened and iterates over all sched domains
/linux-3.4.99/arch/x86/boot/
Dheader.S403 # which happened to work by accident for the old code. Recalculate the stack
/linux-3.4.99/Documentation/
Doops-tracing.txt72 happened in).
106 make fs/buffer.s # or whatever file the bug happened in
Ddma-buf-sharing.txt116 the buffer must have happened before map_dma_buf can be called.
203 - at least one map_dma_buf has happened,
/linux-3.4.99/Documentation/laptops/
Dsony-laptop.txt136 happened to me, this driver could do very bad things to your
/linux-3.4.99/Documentation/sound/alsa/
DProcfile.txt219 happened.
/linux-3.4.99/Documentation/isdn/
DREADME.x2520 this is experimental code, don't blame me if that happened to you.

123