diff options
author | Elyes Haouas <ehaouas@noos.fr> | 2023-06-01 23:41:33 +0000 |
---|---|---|
committer | Warner Losh <imp@FreeBSD.org> | 2023-06-02 02:33:40 +0000 |
commit | 6372f2c8a884b20e65cdea598b055e93ce5a1147 (patch) | |
tree | d81dac87399ddba79eecb9fa4915adcacad092fb | |
parent | 1f0cd2d9ce73ec914040615841a4fc2cb5a02897 (diff) | |
download | src-6372f2c8a884b20e65cdea598b055e93ce5a1147.tar.gz src-6372f2c8a884b20e65cdea598b055e93ce5a1147.zip |
rpc.lockd: Fix typos
Signed-off-by: Elyes Haouas <ehaouas@noos.fr>
Reviewed by: imp
Pull Request: https://github.com/freebsd/freebsd-src/pull/653
-rw-r--r-- | usr.sbin/rpc.lockd/lockd_lock.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/usr.sbin/rpc.lockd/lockd_lock.c b/usr.sbin/rpc.lockd/lockd_lock.c index 66ac74bf0cd2..0bde779642c0 100644 --- a/usr.sbin/rpc.lockd/lockd_lock.c +++ b/usr.sbin/rpc.lockd/lockd_lock.c @@ -759,7 +759,7 @@ get_lock_matching_unlock(const struct file_lock *fl) * This routine makes the following assumptions: * 1) Nothing will adjust the lock list during a lookup * - * This routine has an intersting quirk which bit me hard. + * This routine has an interesting quirk which bit me hard. * The conflicting_fl is the pointer to the conflicting lock. * However, to modify the "*pointer* to the conflicting lock" rather * that the "conflicting lock itself" one must pass in a "pointer to |