From: Conor Dooley <conor@kernel.org>
To: Cleo John <waterdev@galaxycrow.de>
Cc: Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] riscv: fix styling in ucontext header
Date: Mon, 10 Oct 2022 19:50:56 +0100 [thread overview]
Message-ID: <Y0RpkI66dwEKD9Kw@spud> (raw)
In-Reply-To: <20221010182848.GA28029@watet-ms7b87>
On Mon, Oct 10, 2022 at 08:28:48PM +0200, Cleo John wrote:
> Change the two comments in ucontext.h by getting them up to
> the coding style proposed by torvalds.
>
> Signed-off-by: Cleo John <waterdev@galaxycrow.de>
> ---
> In my opinion this also improves the readability so I think this is a useful change to do.
> Please also tell me if you have a different opinion.
I don't think it is all that /important/ of a change, but it does make
things match between this file and the other headers.
Reviewed-by: Conor Dooley <conor.dooley@microchip.com>
Thanks.
>
> Changes in v2:
> - change the styling of the top comments too
>
> arch/riscv/include/uapi/asm/ucontext.h | 12 ++++++++----
> 1 file changed, 8 insertions(+), 4 deletions(-)
>
> diff --git a/arch/riscv/include/uapi/asm/ucontext.h b/arch/riscv/include/uapi/asm/ucontext.h
> index 44eb993950e5..516bd0bb0da5 100644
> --- a/arch/riscv/include/uapi/asm/ucontext.h
> +++ b/arch/riscv/include/uapi/asm/ucontext.h
> @@ -15,19 +15,23 @@ struct ucontext {
> struct ucontext *uc_link;
> stack_t uc_stack;
> sigset_t uc_sigmask;
> - /* There's some padding here to allow sigset_t to be expanded in the
> + /*
> + * There's some padding here to allow sigset_t to be expanded in the
> * future. Though this is unlikely, other architectures put uc_sigmask
> * at the end of this structure and explicitly state it can be
> - * expanded, so we didn't want to box ourselves in here. */
> + * expanded, so we didn't want to box ourselves in here.
> + */
> __u8 __unused[1024 / 8 - sizeof(sigset_t)];
> - /* We can't put uc_sigmask at the end of this structure because we need
> + /*
> + * We can't put uc_sigmask at the end of this structure because we need
> * to be able to expand sigcontext in the future. For example, the
> * vector ISA extension will almost certainly add ISA state. We want
> * to ensure all user-visible ISA state can be saved and restored via a
> * ucontext, so we're putting this at the end in order to allow for
> * infinite extensibility. Since we know this will be extended and we
> * assume sigset_t won't be extended an extreme amount, we're
> - * prioritizing this. */
> + * prioritizing this.
> + */
> struct sigcontext uc_mcontext;
> };
>
> --
> 2.25.1
>
next prev parent reply other threads:[~2022-10-10 18:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-10 18:28 [PATCH v2] riscv: fix styling in ucontext header Cleo John
2022-10-10 18:50 ` Conor Dooley [this message]
2022-10-10 19:55 ` Cleo John
2022-10-10 20:41 ` Conor Dooley
2022-10-19 10:07 ` Cleo John
2022-10-19 10:20 ` Conor Dooley
2022-10-28 22:23 ` Palmer Dabbelt
2022-10-28 22:42 ` Conor Dooley
2022-10-28 22:23 ` Palmer Dabbelt
-- strict thread matches above, loose matches on Subject: below --
2022-10-09 13:13 Cleo John
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Y0RpkI66dwEKD9Kw@spud \
--to=conor@kernel.org \
--cc=aou@eecs.berkeley.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=waterdev@galaxycrow.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox