All of lore.kernel.org
 help / color / mirror / Atom feed
From: Julia Lawall <julia.lawall@inria.fr>
To: R Veera Kumar <vkor@vkten.in>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	 outreachy-kernel <outreachy-kernel@googlegroups.com>
Subject: Re: [Outreachy kernel] [PATCH] staging: rts5208: Fix long line in C func call argument
Date: Sat, 14 Mar 2020 14:47:08 +0100 (CET)	[thread overview]
Message-ID: <alpine.DEB.2.21.2003141444430.3026@hadrien> (raw)
In-Reply-To: <20200314133329.GA1569@tulip.local>



On Sat, 14 Mar 2020, R Veera Kumar wrote:

> On Sat, Mar 14, 2020 at 12:51:16PM +0100, Julia Lawall wrote:
> >
> >
> > On Sat, 14 Mar 2020, R Veera Kumar wrote:
> >
> > > A simple fix of long line in C function call argument.
> >
> > Try to rewrite the whole thing without using the word "fix".  What did you
> > do and why?
> >
> > Simple is not a good word to use, because it is your opinion.  It is
> > probably everyone's opinion in this case, but it is still an opinion.
> >
> > julia
> >
>
> Is subject line ok? I mean the word 'fix' in it.
>
> Is this ok for body:
>
> A correction of long line function call with arguments exceeding the
> 80 columns limit of coding style.

No.

What you did: add a newline after the first argument
Why did you do it: respect the 80 character line limit

I guess one could live with Fix in the subject line, but the current
subject line is too verbose.  All of the code in the kernel is C code, for
example, so there is not much point to mention that.  Something like
"shorten long line" would be fine.

julia

>
> >
> > > Found using checkpatch.pl.
> > >
> > > Signed-off-by: R Veera Kumar <vkor@vkten.in>
> > > ---
> > >  drivers/staging/rts5208/rtsx_chip.c | 3 ++-
> > >  1 file changed, 2 insertions(+), 1 deletion(-)
> > >
> > > diff --git a/drivers/staging/rts5208/rtsx_chip.c b/drivers/staging/rts5208/rtsx_chip.c
> > > index 17c4131f5f62..c6f9375468eb 100644
> > > --- a/drivers/staging/rts5208/rtsx_chip.c
> > > +++ b/drivers/staging/rts5208/rtsx_chip.c
> > > @@ -940,7 +940,8 @@ static void rtsx_monitor_aspm_config(struct rtsx_chip *chip)
> > >  		if (maybe_support_aspm)
> > >  			chip->aspm_l0s_l1_en = 0x03;
> > >
> > > -		dev_dbg(rtsx_dev(chip), "aspm_level[0] = 0x%02x, aspm_level[1] = 0x%02x\n",
> > > +		dev_dbg(rtsx_dev(chip),
> > > +			"aspm_level[0] = 0x%02x, aspm_level[1] = 0x%02x\n",
> > >  			chip->aspm_level[0], chip->aspm_level[1]);
> > >
> > >  		if (chip->aspm_l0s_l1_en) {
> > > --
> > > 2.20.1
> > >
>


      reply	other threads:[~2020-03-14 13:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-14  6:05 [PATCH] staging: rts5208: Fix long line in C func call argument R Veera Kumar
2020-03-14 11:51 ` [Outreachy kernel] " Julia Lawall
2020-03-14 13:33   ` R Veera Kumar
2020-03-14 13:47     ` Julia Lawall [this message]

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=alpine.DEB.2.21.2003141444430.3026@hadrien \
    --to=julia.lawall@inria.fr \
    --cc=gregkh@linuxfoundation.org \
    --cc=outreachy-kernel@googlegroups.com \
    --cc=vkor@vkten.in \
    /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.