From: Maya Nakamura <m.maya.nakamura@gmail.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: outreachy-kernel@googlegroups.com
Subject: Re: [PATCH 3/4] staging: rtlwifi: Add blank lines
Date: Fri, 9 Nov 2018 02:15:32 -0800 [thread overview]
Message-ID: <20181109101531.GA121437@m-hyperV> (raw)
In-Reply-To: <20181108112857.GB23141@kroah.com>
On Thu, Nov 08, 2018 at 03:28:57AM -0800, Greg KH wrote:
> On Wed, Nov 07, 2018 at 11:23:07PM -0800, Maya Nakamura wrote:
> > Add blank lines after if statements.
>
> That says what you did, but not _why_ you did this.
>
> >
> > Signed-off-by: Maya Nakamura <m.maya.nakamura@gmail.com>
> > ---
> > drivers/staging/rtlwifi/phydm/phydm_adc_sampling.c | 1 +
> > drivers/staging/rtlwifi/phydm/phydm_ccx.c | 1 +
> > 2 files changed, 2 insertions(+)
> >
> > diff --git a/drivers/staging/rtlwifi/phydm/phydm_adc_sampling.c b/drivers/staging/rtlwifi/phydm/phydm_adc_sampling.c
> > index 7eb54d2e48f3..7d578241326b 100644
> > --- a/drivers/staging/rtlwifi/phydm/phydm_adc_sampling.c
> > +++ b/drivers/staging/rtlwifi/phydm/phydm_adc_sampling.c
> > @@ -563,6 +563,7 @@ void phydm_lamode_trigger_setting(void *dm_void, char input[][16], u32 *_used,
> > PHYDM_SSCANF(input[3], DCMD_HEX, &var1[2]);
> > else
> > PHYDM_SSCANF(input[3], DCMD_DECIMAL, &var1[2]);
> > +
> > trig_sig_sel = var1[2];
> >
> > PHYDM_SSCANF(input[4], DCMD_DECIMAL, &var1[3]);
> > diff --git a/drivers/staging/rtlwifi/phydm/phydm_ccx.c b/drivers/staging/rtlwifi/phydm/phydm_ccx.c
> > index ded6642bdf64..c0da601be6cf 100644
> > --- a/drivers/staging/rtlwifi/phydm/phydm_ccx.c
> > +++ b/drivers/staging/rtlwifi/phydm/phydm_ccx.c
> > @@ -357,6 +357,7 @@ bool phydm_check_nhm_ready(void *dm_void)
> > }
> > }
> > }
> > +
>
> Is this one really needed?
>
> thanks,
>
> greg k-h
Hi Greg,
Thank you for accepting three of my four patches in this patchset!
I read several examples that use if statements in K&R and didn't find a
blank line between them and the next statements. I thought that it is
easier to read with a blank line, but it is just my personal preference,
so it is not necessary. Therefore, I won't resubmit this patch.
Maya
next prev parent reply other threads:[~2018-11-09 10:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-08 7:20 [PATCH 0/4] staging: rtlwifi: Change line and comment spacing Maya Nakamura
2018-11-08 7:21 ` [PATCH 1/4] staging: rtlwifi: Improve line endings Maya Nakamura
2018-11-08 7:22 ` [PATCH 2/4] staging: rtlwifi: Remove empty comment Maya Nakamura
2018-11-08 7:23 ` [PATCH 3/4] staging: rtlwifi: Add blank lines Maya Nakamura
2018-11-08 11:28 ` Greg KH
2018-11-09 10:15 ` Maya Nakamura [this message]
2018-11-08 7:23 ` [PATCH 4/4] staging: rtlwifi: Add spaces for comments Maya Nakamura
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=20181109101531.GA121437@m-hyperV \
--to=m.maya.nakamura@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=outreachy-kernel@googlegroups.com \
/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.