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
No, the first case is true.
spin_xxx are defined as macros, you do not need referencing the lock variable to pass it. Furthermore, using plain spin_lock/spin_unlock does not make sense in uniprocessor systems, particularly in embox, these macros are defined as no-op
(src/linux-compat/include/linux/spinlock.h).
To protect data in interrupt context you should use spin_lock_irqsave(lock, flags) and spin_unlock_irqrestore(lock, flags).
functions 'spin_lock' and 'spin_unlock' in net_pack_manager.c are used with wrong interface
must be
The text was updated successfully, but these errors were encountered: