All of lore.kernel.org
 help / color / mirror / Atom feed
From: greg at kroah.com (Greg KH)
Subject: [Linux-kernel-mentees] [PATCH] Staging: rtl8192u: ieee80211: Fix comment formating errors
Date: Fri, 3 May 2019 10:01:25 +0200	[thread overview]
Message-ID: <20190503080125.GB14960@kroah.com> (raw)
In-Reply-To: <20190503075204.GB4313@arch>

On Fri, May 03, 2019 at 01:22:04PM +0530, Puranjay Mohan wrote:
> On Thu, May 02, 2019 at 07:41:54PM +0200, Greg KH wrote:
> > On Thu, May 02, 2019 at 10:56:08AM +0530, Puranjay Mohan wrote:
> > > Fix comment formating warnings found by checkpatch.pl
> > > 
> > > Signed-off-by: Puranjay Mohan <puranjay12 at gmail.com>
> > > ---
> > >  .../rtl8192u/ieee80211/ieee80211_softmac.c    | 66 ++++++++++---------
> > >  1 file changed, 34 insertions(+), 32 deletions(-)
> > > 
> > > diff --git a/drivers/staging/rtl8192u/ieee80211/ieee80211_softmac.c b/drivers/staging/rtl8192u/ieee80211/ieee80211_softmac.c
> > > index 944c8894f9ff..be02f73f5618 100644
> > > --- a/drivers/staging/rtl8192u/ieee80211/ieee80211_softmac.c
> > > +++ b/drivers/staging/rtl8192u/ieee80211/ieee80211_softmac.c
> > > @@ -196,13 +196,13 @@ static u8 MgntQuery_MgntFrameTxRate(struct ieee80211_device *ieee)
> > >  	}
> > >  
> > >  	/*
> > > -	// Data rate of ProbeReq is already decided. Annie, 2005-03-31
> > > -	if( pMgntInfo->bScanInProgress || (pMgntInfo->bDualModeScanStep!=0) ) {
> > > -	if(pMgntInfo->dot11CurrentWirelessMode==WIRELESS_MODE_A)
> > > -	rate = 0x0c;
> > > -	else
> > > -	rate = 0x02;
> > > -	}
> > > +	 * // Data rate of ProbeReq is already decided. Annie, 2005-03-31
> > > +	 * if( pMgntInfo->bScanInProgress || (pMgntInfo->bDualModeScanStep!=0) ) {
> > > +	 * if(pMgntInfo->dot11CurrentWirelessMode==WIRELESS_MODE_A)
> > > +	 * rate = 0x0c;
> > > +	 * else
> > > +	 * rate = 0x02;
> > > +	 * }
> > >  	 */
> > >  	return rate;
> > 
> > Ick, no, just delete this chunk, that indentation makes no sense.
> This solves this checkpatch.pl warning
> WARNING: Block comments use * on subsequent lines

checkpatch.pl is only a dumb perl script, it can't know about
everything, you have to always take its advice under advisement, it is
not always correct.

Look at the change you made, does it really make much sense?  Does the
code look better after you have made it?  That's the key here, your goal
is to leave the code better looking and easier to understand overall.
Just indenting the comment does not really do that.

> I have fixed all trailing whitespace issues, also fixed my editor to
> show them :D.
> Should I keep the above two blocks(which you told to remove) in V2
> because they solve WARNING:Block comments use * on subsequent lines,
> or should I remove them before sending V2.

Please remove and send them as a different patch that removes commented
out code.

thanks,

greg k-h

WARNING: multiple messages have this Message-ID (diff)
From: greg@kroah.com (Greg KH)
Subject: [Linux-kernel-mentees] [PATCH] Staging: rtl8192u: ieee80211: Fix comment formating errors
Date: Fri, 3 May 2019 10:01:25 +0200	[thread overview]
Message-ID: <20190503080125.GB14960@kroah.com> (raw)
Message-ID: <20190503080125.HnTPQyxoAzxgLxVUsrbmzkzh3FmgOjskhPcucQZoeiA@z> (raw)
In-Reply-To: <20190503075204.GB4313@arch>

On Fri, May 03, 2019 at 01:22:04PM +0530, Puranjay Mohan wrote:
> On Thu, May 02, 2019 at 07:41:54PM +0200, Greg KH wrote:
> > On Thu, May 02, 2019 at 10:56:08AM +0530, Puranjay Mohan wrote:
> > > Fix comment formating warnings found by checkpatch.pl
> > > 
> > > Signed-off-by: Puranjay Mohan <puranjay12 at gmail.com>
> > > ---
> > >  .../rtl8192u/ieee80211/ieee80211_softmac.c    | 66 ++++++++++---------
> > >  1 file changed, 34 insertions(+), 32 deletions(-)
> > > 
> > > diff --git a/drivers/staging/rtl8192u/ieee80211/ieee80211_softmac.c b/drivers/staging/rtl8192u/ieee80211/ieee80211_softmac.c
> > > index 944c8894f9ff..be02f73f5618 100644
> > > --- a/drivers/staging/rtl8192u/ieee80211/ieee80211_softmac.c
> > > +++ b/drivers/staging/rtl8192u/ieee80211/ieee80211_softmac.c
> > > @@ -196,13 +196,13 @@ static u8 MgntQuery_MgntFrameTxRate(struct ieee80211_device *ieee)
> > >  	}
> > >  
> > >  	/*
> > > -	// Data rate of ProbeReq is already decided. Annie, 2005-03-31
> > > -	if( pMgntInfo->bScanInProgress || (pMgntInfo->bDualModeScanStep!=0) ) {
> > > -	if(pMgntInfo->dot11CurrentWirelessMode==WIRELESS_MODE_A)
> > > -	rate = 0x0c;
> > > -	else
> > > -	rate = 0x02;
> > > -	}
> > > +	 * // Data rate of ProbeReq is already decided. Annie, 2005-03-31
> > > +	 * if( pMgntInfo->bScanInProgress || (pMgntInfo->bDualModeScanStep!=0) ) {
> > > +	 * if(pMgntInfo->dot11CurrentWirelessMode==WIRELESS_MODE_A)
> > > +	 * rate = 0x0c;
> > > +	 * else
> > > +	 * rate = 0x02;
> > > +	 * }
> > >  	 */
> > >  	return rate;
> > 
> > Ick, no, just delete this chunk, that indentation makes no sense.
> This solves this checkpatch.pl warning
> WARNING: Block comments use * on subsequent lines

checkpatch.pl is only a dumb perl script, it can't know about
everything, you have to always take its advice under advisement, it is
not always correct.

Look at the change you made, does it really make much sense?  Does the
code look better after you have made it?  That's the key here, your goal
is to leave the code better looking and easier to understand overall.
Just indenting the comment does not really do that.

> I have fixed all trailing whitespace issues, also fixed my editor to
> show them :D.
> Should I keep the above two blocks(which you told to remove) in V2
> because they solve WARNING:Block comments use * on subsequent lines,
> or should I remove them before sending V2.

Please remove and send them as a different patch that removes commented
out code.

thanks,

greg k-h

  reply	other threads:[~2019-05-03  8:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-02  5:26 [Linux-kernel-mentees] [PATCH] Staging: rtl8192u: ieee80211: Fix comment formating errors puranjay12
2019-05-02  5:26 ` Puranjay Mohan
2019-05-02 17:41 ` greg
2019-05-02 17:41   ` Greg KH
2019-05-03  7:52   ` puranjay12
2019-05-03  7:52     ` Puranjay Mohan
2019-05-03  8:01     ` greg [this message]
2019-05-03  8:01       ` Greg KH

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=20190503080125.GB14960@kroah.com \
    --to=unknown@example.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.