You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The gpio_free_array function was incorrectly passed ARRAY_SIZE(leds)
when freeing the 'buttons' array in multiple examples:
- examples/intrp.c
- examples/bottomhalf.c
- examples/bh_halfthreaded.c
This mismatch could lead to invalid memory access if the size of
'buttons' differs from 'leds'.
Updated all occurrences to use ARRAY_SIZE(buttons) for correctness.
Co-authored-by: EricccTaiwan <yphbchou0911@gmail.com>
Signed-off-by: Jordan Chiu <jordan871130@gmail.com>
Copy file name to clipboardExpand all lines: lkmpg.tex
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -1778,7 +1778,7 @@ \subsection{Spinlocks}
1778
1778
In contrast, \cpp|spin_lock_irqsave()| disables interrupts and also saves the interrupt state, ensuring that interrupts are restored to their previous state when the lock is released.
1779
1779
This makes \cpp|spin_lock_irqsave()| a safer option in scenarios where preserving the interrupt state is crucial.
1780
1780
1781
-
Next, \cpp|spin_lock_bh()| disables softirqs (software interrupts) but allows hardware interrupts to continue.
1781
+
Next, \cpp|spin_lock_bh()| disables \textbf{softirqs} (software interrupts) but allows hardware interrupts to continue.
1782
1782
Unlike \cpp|spin_lock_irq()| and \cpp|spin_lock_irqsave()|, which disable both hardware and software interrupts, \cpp|spin_lock_bh()| is useful when hardware interrupts need to remain active.
1783
1783
1784
1784
For more information about spinlock usage and lock types, see the following resources:
0 commit comments