diff options
author | Michael Tokarev <mjt@tls.msk.ru> | 2023-07-14 14:06:43 +0300 |
---|---|---|
committer | Michael Tokarev <mjt@tls.msk.ru> | 2023-09-20 07:54:34 +0300 |
commit | 944399ffb286b5503e9d97330aaeab1e68779962 (patch) | |
tree | 75d1b68a73fbcbd58d8043fa5d57bd7b13876bcf /bsd-user/signal.c | |
parent | e6a19a6477407e57b4deb61aaa497a14d7db9626 (diff) | |
download | qemu-944399ffb286b5503e9d97330aaeab1e68779962.zip qemu-944399ffb286b5503e9d97330aaeab1e68779962.tar.gz qemu-944399ffb286b5503e9d97330aaeab1e68779962.tar.bz2 |
bsd-user: spelling fixes
Signed-off-by: Michael Tokarev <mjt@tls.msk.ru>
Reviewed-by: Kyle Evans <kevans@FreeBSD.org>
Reviewed-by: Warner Losh <imp@bsdimp.com>
Diffstat (limited to 'bsd-user/signal.c')
-rw-r--r-- | bsd-user/signal.c | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/bsd-user/signal.c b/bsd-user/signal.c index 4db85a3..b6beab6 100644 --- a/bsd-user/signal.c +++ b/bsd-user/signal.c @@ -44,7 +44,7 @@ static inline int sas_ss_flags(TaskState *ts, unsigned long sp) } /* - * The BSD ABIs use the same singal numbers across all the CPU architectures, so + * The BSD ABIs use the same signal numbers across all the CPU architectures, so * (unlike Linux) these functions are just the identity mapping. This might not * be true for XyzBSD running on AbcBSD, which doesn't currently work. */ @@ -241,7 +241,7 @@ static inline void host_to_target_siginfo_noswap(target_siginfo_t *tinfo, #endif /* * Unsure that this can actually be generated, and our support for - * capsicum is somewhere between weak and non-existant, but if we get + * capsicum is somewhere between weak and non-existent, but if we get * one, then we know what to save. */ #ifdef QEMU_SI_CAPSICUM @@ -319,7 +319,7 @@ int block_signals(void) /* * It's OK to block everything including SIGSEGV, because we won't run any * further guest code before unblocking signals in - * process_pending_signals(). We depend on the FreeBSD behaivor here where + * process_pending_signals(). We depend on the FreeBSD behavior here where * this will only affect this thread's signal mask. We don't use * pthread_sigmask which might seem more correct because that routine also * does odd things with SIGCANCEL to implement pthread_cancel(). |