All of lore.kernel.org
 help / color / mirror / Atom feed
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] Fixed styling in riscv ucontext header
Date: Sun, 9 Oct 2022 13:43:02 +0100	[thread overview]
Message-ID: <Y0LB1oLuVIytgKI/@spud> (raw)
In-Reply-To: <1923489.PYKUYFuaPT@watet-ms7b87>

On Sun, Oct 09, 2022 at 02:38:43PM +0200, Cleo John wrote:
> Hey Connor,
> 
> On Sun, 9. October 2022, 14:14:52 CEST, Conor Dooley wrote:
> > Hey Cleo,
> > 
> > On Sun, Oct 09, 2022 at 02:03:40PM +0200, Cleo John wrote:
> > > Fixed styling in riscv ucontext header
> > 
> > This should probably be "riscv: fix styling..."
> 
> okay yea, I will change this in a second patch.
> 
> > > This patch changes the two comments in ucontext.h by getting them up to
> > > the cody style proposed by torwalds.
> > s/This patch changes/Change
> > 
> > Looks like some typos here too & your lines need to be wrapped at 72
> > characters for commit messages. git usually enforces that automatically
> > when you do a `git commit`.
> I will wrap the lines, but where are the typos if I may ask?
>

"cody style" & s/w/v/ in Linus' name.

> > > 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.
> > 
> > FYI commentary on the patch should go below the ---.
> will note
> 
> > > Signed-off-by: Cleo John <waterdev@galaxycrow.de>
> > > ---
> > > 
> > >  arch/riscv/include/uapi/asm/ucontext.h | 6 ++++--
> > >  1 file changed, 4 insertions(+), 2 deletions(-)
> > > 
> > > diff --git a/arch/riscv/include/uapi/asm/ucontext.h
> > > b/arch/riscv/include/uapi/asm/ucontext.h index 44eb993950e5..0cd6f8616985
> > > 100644
> > > --- a/arch/riscv/include/uapi/asm/ucontext.h
> > > +++ b/arch/riscv/include/uapi/asm/ucontext.h
> > > @@ -18,7 +18,8 @@ struct ucontext {
> > > 
> > >  	/* There's some padding here to allow sigset_t to be expanded in 
> the
> > 
> > Why fix the closing comment but leave the opening ones incorrect?
> > 
> > Thanks,
> > Conor.
> 
> I mixed the code style up with the one in net/ -will fix
> 
> Thanks,
> Cleo.
> 
> > >  	 * 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
> > >  	
> > >  	 * to be able to expand sigcontext in the future.  For example, 
> the
> > > 
> > > @@ -27,7 +28,8 @@ struct ucontext {
> > > 
> > >  	 * 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;
> > >  
> > >  };
> 



_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

WARNING: multiple messages have this Message-ID (diff)
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] Fixed styling in riscv ucontext header
Date: Sun, 9 Oct 2022 13:43:02 +0100	[thread overview]
Message-ID: <Y0LB1oLuVIytgKI/@spud> (raw)
In-Reply-To: <1923489.PYKUYFuaPT@watet-ms7b87>

On Sun, Oct 09, 2022 at 02:38:43PM +0200, Cleo John wrote:
> Hey Connor,
> 
> On Sun, 9. October 2022, 14:14:52 CEST, Conor Dooley wrote:
> > Hey Cleo,
> > 
> > On Sun, Oct 09, 2022 at 02:03:40PM +0200, Cleo John wrote:
> > > Fixed styling in riscv ucontext header
> > 
> > This should probably be "riscv: fix styling..."
> 
> okay yea, I will change this in a second patch.
> 
> > > This patch changes the two comments in ucontext.h by getting them up to
> > > the cody style proposed by torwalds.
> > s/This patch changes/Change
> > 
> > Looks like some typos here too & your lines need to be wrapped at 72
> > characters for commit messages. git usually enforces that automatically
> > when you do a `git commit`.
> I will wrap the lines, but where are the typos if I may ask?
>

"cody style" & s/w/v/ in Linus' name.

> > > 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.
> > 
> > FYI commentary on the patch should go below the ---.
> will note
> 
> > > Signed-off-by: Cleo John <waterdev@galaxycrow.de>
> > > ---
> > > 
> > >  arch/riscv/include/uapi/asm/ucontext.h | 6 ++++--
> > >  1 file changed, 4 insertions(+), 2 deletions(-)
> > > 
> > > diff --git a/arch/riscv/include/uapi/asm/ucontext.h
> > > b/arch/riscv/include/uapi/asm/ucontext.h index 44eb993950e5..0cd6f8616985
> > > 100644
> > > --- a/arch/riscv/include/uapi/asm/ucontext.h
> > > +++ b/arch/riscv/include/uapi/asm/ucontext.h
> > > @@ -18,7 +18,8 @@ struct ucontext {
> > > 
> > >  	/* There's some padding here to allow sigset_t to be expanded in 
> the
> > 
> > Why fix the closing comment but leave the opening ones incorrect?
> > 
> > Thanks,
> > Conor.
> 
> I mixed the code style up with the one in net/ -will fix
> 
> Thanks,
> Cleo.
> 
> > >  	 * 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
> > >  	
> > >  	 * to be able to expand sigcontext in the future.  For example, 
> the
> > > 
> > > @@ -27,7 +28,8 @@ struct ucontext {
> > > 
> > >  	 * 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;
> > >  
> > >  };
> 



  reply	other threads:[~2022-10-09 12:43 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-09 12:03 [PATCH] Fixed styling in riscv ucontext header Cleo John
2022-10-09 12:03 ` Cleo John
2022-10-09 12:14 ` Conor Dooley
2022-10-09 12:14   ` Conor Dooley
2022-10-09 12:38   ` Cleo John
2022-10-09 12:38     ` Cleo John
2022-10-09 12:43     ` Conor Dooley [this message]
2022-10-09 12:43       ` Conor Dooley
2022-10-09 12:49       ` Cleo John
2022-10-09 12:49         ` 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=Y0LB1oLuVIytgKI/@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.