All of lore.kernel.org
 help / color / mirror / Atom feed
From: R Veera Kumar <vkor@vkten.in>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: outreachy-kernel <outreachy-kernel@googlegroups.com>
Subject: Re: [PATCH 1/2] staging: rtl8723bs: os_dep: Correct long line comments
Date: Sat, 21 Mar 2020 07:44:18 +0530	[thread overview]
Message-ID: <20200321021416.GA569@tulip.local> (raw)
In-Reply-To: <20200320140516.GA643325@kroah.com>

On Fri, Mar 20, 2020 at 03:05:16PM +0100, Greg Kroah-Hartman wrote:
> On Fri, Mar 20, 2020 at 07:08:22AM +0530, R Veera Kumar wrote:
> > Correct long line comments to respect 80 character per
> > line limit.
> > 
> > diff --git a/drivers/staging/rtl8723bs/os_dep/recv_linux.c b/drivers/staging/rtl8723bs/os_dep/recv_linux.c
> > index a6491f163272..87090af7d776 100644
> > --- a/drivers/staging/rtl8723bs/os_dep/recv_linux.c
> > +++ b/drivers/staging/rtl8723bs/os_dep/recv_linux.c
> > @@ -35,7 +35,8 @@ void rtw_os_recv_resource_free(struct recv_priv *precvpriv)
> >  
> >  			if (memcmp(pattrib->dst, myid(&padapter->eeprompriv), ETH_ALEN)) {
> > -				/* DBG_871X("not ap psta =%p, addr =%pM\n", psta, pattrib->dst); */
> > +				/*
> > +				 * DBG_871X("not ap psta =%p, addr =%pM\n",
> > +				 * psta, pattrib->dst);
> 
> Again, this is not a long-line comment, it is a code line that is
> commented out.  Remove it in a patch previous to this one please.
>

Okay I understand now that it is not a valid comment describing how
it functions.

But is not that the developers intention was to keep this to remind
him of doing something.

Or should he should have kept in his codebase and not here.

Also should I create a patch to remove this commented out code lines
in the same patch series or a new one.

Veera

> > +				 */
> >  
> >  				if (bmcast) {
> >  					psta = rtw_get_bcmc_stainfo(padapter);
> > @@ -124,7 +131,10 @@ void rtw_os_recv_indicate_pkt(struct adapter *padapter, _pkt *pkt, struct rx_pkt
> >  				if (psta) {
> >  					struct net_device *pnetdev = (struct net_device*)padapter->pnetdev;
> >  
> > -					/* DBG_871X("directly forwarding to the rtw_xmit_entry\n"); */
> > +					/*
> > +					 * DBG_871X("directly forwarding to the
> > +					 * rtw_xmit_entry\n");
> 
> Same here.
> 
> thanks,
> 
> greg k-h


  reply	other threads:[~2020-03-21  2:14 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-20  1:38 [PATCH 0/2] Correct long line comments and remove whitespace in code R Veera Kumar
2020-03-20  1:38 ` [PATCH 1/2] staging: rtl8723bs: os_dep: Correct long line comments R Veera Kumar
2020-03-20 14:05   ` Greg Kroah-Hartman
2020-03-21  2:14     ` R Veera Kumar [this message]
2020-03-21  7:35       ` [Outreachy kernel] " Julia Lawall
2020-03-20  1:38 ` [PATCH 2/2] staging: rtl8723bs: os_dep: Remove whitespace characters in code line R Veera Kumar
2020-03-20 14:05   ` Greg Kroah-Hartman
2020-03-20 16:49     ` R Veera Kumar

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=20200321021416.GA569@tulip.local \
    --to=vkor@vkten.in \
    --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.