From 01f623d345aa787074d30f56b34aa1c00090b9bc Mon Sep 17 00:00:00 2001
From: Jesper Juhl <jj@chaosbits.net>
Date: Sun, 17 Jul 2011 21:15:54 +0200
Subject: [PATCH] --- yaml --- r: 258878 b: refs/heads/master c:
 06b72d06d6b182bdaaaec686dbd8b602949521ee h: refs/heads/master v: v3

---
 [refs]                   | 2 +-
 trunk/drivers/uwb/uwbd.c | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/[refs] b/[refs]
index da2c36ba578b..5fd93e333970 100644
--- a/[refs]
+++ b/[refs]
@@ -1,2 +1,2 @@
 ---
-refs/heads/master: f0da7ee410e63a1521af734c3970acc1470e8c50
+refs/heads/master: 06b72d06d6b182bdaaaec686dbd8b602949521ee
diff --git a/trunk/drivers/uwb/uwbd.c b/trunk/drivers/uwb/uwbd.c
index 001c8b4020a8..bdcb13cc1d54 100644
--- a/trunk/drivers/uwb/uwbd.c
+++ b/trunk/drivers/uwb/uwbd.c
@@ -256,7 +256,7 @@ static void uwbd_event_handle(struct uwb_event *evt)
  * UWB Daemon
  *
  * Listens to all UWB notifications and takes care to track the state
- * of the UWB neighboorhood for the kernel. When we do a run, we
+ * of the UWB neighbourhood for the kernel. When we do a run, we
  * spinlock, move the list to a private copy and release the
  * lock. Hold it as little as possible. Not a conflict: it is
  * guaranteed we own the events in the private list.