[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20201206085134.GS1370092@port70.net>
Date: Sun, 6 Dec 2020 09:51:34 +0100
From: Szabolcs Nagy <nsz@...t70.net>
To: Drew DeVault <sir@...wn.com>
Cc: musl@...ts.openwall.com
Subject: Re: [PATCH v2] riscv64: correct struct __ucontext name
* Drew DeVault <sir@...wn.com> [2020-12-05 18:10:06 +0000]:
> This makes it consistent with other architectures and fixes some issues
> with downstream software.
which software?
glibc uses struct ucontext_t too and user code should use ucontext_t
without struct.
> ---
> v1 missed a spot. Please Cc me on replies.
>
> arch/riscv64/bits/signal.h | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/arch/riscv64/bits/signal.h b/arch/riscv64/bits/signal.h
> index b006334f..287367db 100644
> --- a/arch/riscv64/bits/signal.h
> +++ b/arch/riscv64/bits/signal.h
> @@ -60,10 +60,10 @@ struct sigaltstack {
> size_t ss_size;
> };
>
> -typedef struct ucontext_t
> +typedef struct __ucontext
> {
> unsigned long uc_flags;
> - struct ucontext_t *uc_link;
> + struct __ucontext *uc_link;
> stack_t uc_stack;
> sigset_t uc_sigmask;
> mcontext_t uc_mcontext;
> --
> 2.29.2
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
