From owner-p4-projects Tue Mar 4 13:26:51 2003 Delivered-To: p4-projects@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 32767) id B472C37B405; Tue, 4 Mar 2003 13:26:49 -0800 (PST) Delivered-To: perforce@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4B31C37B401 for ; Tue, 4 Mar 2003 13:26:49 -0800 (PST) Received: from repoman.freebsd.org (repoman.freebsd.org [216.136.204.115]) by mx1.FreeBSD.org (Postfix) with ESMTP id EB38843F3F for ; Tue, 4 Mar 2003 13:26:48 -0800 (PST) (envelope-from jhb@freebsd.org) Received: from repoman.freebsd.org (localhost [127.0.0.1]) by repoman.freebsd.org (8.12.6/8.12.6) with ESMTP id h24LQm0U063816 for ; Tue, 4 Mar 2003 13:26:48 -0800 (PST) (envelope-from jhb@freebsd.org) Received: (from perforce@localhost) by repoman.freebsd.org (8.12.6/8.12.6/Submit) id h24LQmkM063805 for perforce@freebsd.org; Tue, 4 Mar 2003 13:26:48 -0800 (PST) Date: Tue, 4 Mar 2003 13:26:48 -0800 (PST) Message-Id: <200303042126.h24LQmkM063805@repoman.freebsd.org> X-Authentication-Warning: repoman.freebsd.org: perforce set sender to jhb@freebsd.org using -f From: John Baldwin Subject: PERFORCE change 26341 for review To: Perforce Change Reviews Sender: owner-p4-projects@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG http://perforce.freebsd.org/chv.cgi?CH=26341 Change 26341 by jhb@jhb_laptop on 2003/03/04 13:26:17 Grammar. Affected files ... .. //depot/projects/smpng/sys/kern/subr_witness.c#74 edit Differences ... ==== //depot/projects/smpng/sys/kern/subr_witness.c#74 (text+ko) ==== @@ -1460,11 +1460,11 @@ } /* - * This is a bit risky at best. We have call this when we have timed out - * acquiring a spin lock and are assuming that the other CPU is stuck with - * this lock held. So, we go groveling around in the other CPU's per-cpu - * data to try and find the lock instance for this spin lock to see when it - * was last acquired. + * This is a bit risky at best. We call this function when we have timed + * out acquiring a spin lock, and we assume that the other CPU is stuck + * with this lock held. So, we go groveling around in the other CPU's + * per-cpu data to try to find the lock instance for this spin lock to + * see when it was last acquired. */ void witness_display_spinlock(struct lock_object *lock, struct thread *owner) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe p4-projects" in the body of the message