From 48bbca816818409505a6e214d0911fda44e622e3 Mon Sep 17 00:00:00 2001 From: Daniel Hoffman Date: Fri, 17 Feb 2017 11:48:20 -0800 Subject: 7812 Remove gender specific language Reviewed by: Matt Ahrens Reviewed by: Prakash Surya Reviewed by: Steve Gonczi Reviewed by: Chris Williamson Reviewed by: George Wilson Reviewed by: Igor Kozhukhov Reviewed by: Dan McDonald Reviewed by: Robert Mustacchi Approved by: Richard Lowe --- usr/src/uts/common/os/mutex.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) (limited to 'usr/src/uts/common/os/mutex.c') diff --git a/usr/src/uts/common/os/mutex.c b/usr/src/uts/common/os/mutex.c index a309ca89a3..e9806795d3 100644 --- a/usr/src/uts/common/os/mutex.c +++ b/usr/src/uts/common/os/mutex.c @@ -21,6 +21,7 @@ /* * Copyright 2009 Sun Microsystems, Inc. All rights reserved. * Use is subject to license terms. + * Copyright (c) 2016 by Delphix. All rights reserved. */ /* @@ -149,7 +150,7 @@ * * In many ways (1) is the cleanest solution, but if a lock is moderately * contended it defeats the adaptive spin logic. If we make some other - * thread the owner, but he's not ONPROC yet, then all other threads on + * thread the owner, but it's not ONPROC yet, then all other threads on * other cpus that try to get the lock will conclude that the owner is * blocked, so they'll block too. And so on -- it escalates quickly, * with every thread taking the blocking path rather than the spin path. -- cgit v1.2.3