Date: Tue, 20 Jan 2009 23:25:27 +0000 (UTC) From: Maksim Yevmenkin <emax@FreeBSD.org> To: src-committers@freebsd.org, svn-src-all@freebsd.org, svn-src-head@freebsd.org Subject: svn commit: r187505 - head/sys/dev/usb2/bluetooth Message-ID: <200901202325.n0KNPR0A060226@svn.freebsd.org>
next in thread | raw e-mail | index | archive | help
Author: emax Date: Tue Jan 20 23:25:27 2009 New Revision: 187505 URL: http://svn.freebsd.org/changeset/base/187505 Log: Fix typo in comment Pointed out by: Daan Vreeken / Daan at vehosting dot nl Modified: head/sys/dev/usb2/bluetooth/ng_ubt2.c Modified: head/sys/dev/usb2/bluetooth/ng_ubt2.c ============================================================================== --- head/sys/dev/usb2/bluetooth/ng_ubt2.c Tue Jan 20 23:20:09 2009 (r187504) +++ head/sys/dev/usb2/bluetooth/ng_ubt2.c Tue Jan 20 23:25:27 2009 (r187505) @@ -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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200901202325.n0KNPR0A060226>