Index: kernel/generic/src/synch/condvar.c
===================================================================
--- kernel/generic/src/synch/condvar.c	(revision b7fd2a02e4161f4edd38548e7f8456b8021549be)
+++ kernel/generic/src/synch/condvar.c	(revision 3061bc129a855122d429fbba1e623a521aaa164c)
@@ -107,5 +107,5 @@
 
 /** Wait for the condition to become true with a locked spinlock.
- * 
+ *
  * The function is not aware of irq_spinlock. Therefore do not even
  * try passing irq_spinlock_t to it. Use _condvar_wait_timeout_irq_spinlock()
@@ -124,5 +124,5 @@
  * @return See comment for waitq_sleep_timeout().
  */
-errno_t _condvar_wait_timeout_spinlock_impl(condvar_t *cv, spinlock_t *lock, 
+errno_t _condvar_wait_timeout_spinlock_impl(condvar_t *cv, spinlock_t *lock,
 	uint32_t usec, int flags)
 {
@@ -148,5 +148,5 @@
 
 /** Wait for the condition to become true with a locked irq spinlock.
- * 
+ *
  * @param cv		Condition variable.
  * @param lock		Locked irq spinlock.
@@ -161,5 +161,5 @@
  * @return See comment for waitq_sleep_timeout().
  */
-errno_t _condvar_wait_timeout_irq_spinlock(condvar_t *cv, irq_spinlock_t *irq_lock, 
+errno_t _condvar_wait_timeout_irq_spinlock(condvar_t *cv, irq_spinlock_t *irq_lock,
 	uint32_t usec, int flags)
 {
@@ -171,12 +171,12 @@
 	irq_lock->guard = false;
 	
-	/* 
-	 * waitq_prepare() restores interrupts to the current state, 
-	 * ie disabled. Therefore, interrupts will remain disabled while 
-	 * it spins waiting for a pending timeout handler to complete. 
+	/*
+	 * waitq_prepare() restores interrupts to the current state,
+	 * ie disabled. Therefore, interrupts will remain disabled while
+	 * it spins waiting for a pending timeout handler to complete.
 	 * Although it spins with interrupts disabled there can only
 	 * be a pending timeout if we failed to cancel an imminent
-	 * timeout (on another cpu) during a wakeup. As a result the 
-	 * timeout handler is guaranteed to run (it is most likely already 
+	 * timeout (on another cpu) during a wakeup. As a result the
+	 * timeout handler is guaranteed to run (it is most likely already
 	 * running) and there is no danger of a deadlock.
 	 */
