diff options
| author | emax <emax@FreeBSD.org> | 2009-01-20 23:25:27 +0000 |
|---|---|---|
| committer | emax <emax@FreeBSD.org> | 2009-01-20 23:25:27 +0000 |
| commit | 36a4d5f97544df147bc5680c572cff2194d23bdd (patch) | |
| tree | 6d4c023ccd85b82f6c7bbef7540c4df994b19082 | |
| parent | e276e80f5122ba78bf154e176e16714396df4fb1 (diff) | |
| download | FreeBSD-src-36a4d5f97544df147bc5680c572cff2194d23bdd.zip FreeBSD-src-36a4d5f97544df147bc5680c572cff2194d23bdd.tar.gz | |
Fix typo in comment
Pointed out by: Daan Vreeken / Daan at vehosting dot nl
| -rw-r--r-- | sys/dev/usb2/bluetooth/ng_ubt2.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/sys/dev/usb2/bluetooth/ng_ubt2.c b/sys/dev/usb2/bluetooth/ng_ubt2.c index 668b3ce..a2fbf38 100644 --- a/sys/dev/usb2/bluetooth/ng_ubt2.c +++ b/sys/dev/usb2/bluetooth/ng_ubt2.c @@ -64,7 +64,7 @@ * Netgraph point of view). Any variable that is only modified from the * Netgraph context does not require any additonal locking. It is generally * *NOT* allowed to grab *ANY* additional lock. Whatever you do, *DO NOT* - * not grab any long-sleep lock in the Netgraph context. In fact, the only + * grab any long-sleep lock in the Netgraph context. In fact, the only * lock that is allowed in the Netgraph context is the sc_mbufq_mtx lock. * * 3) Taskqueue context. This is where ubt_task runs. Since we are NOT allowed |
