public inbox for linux-staging@lists.linux.dev
 help / color / mirror / Atom feed
From: Dan Carpenter <dan.carpenter@linaro.org>
To: Ethan Tidmore <ethantidmore06@gmail.com>
Cc: MrXploisLite <arokigaming@gmail.com>,
	gregkh@linuxfoundation.org, linux-staging@lists.linux.dev,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: rtl8723bs: remove spaces before tabs in hal_com.c
Date: Fri, 27 Mar 2026 11:03:39 +0300	[thread overview]
Message-ID: <acY52ww-3P1bkdsn@stanley.mountain> (raw)
In-Reply-To: <DHCX1V89Z0X8.FWX3O4KWXA9Q@gmail.com>

On Thu, Mar 26, 2026 at 01:13:25PM -0500, Ethan Tidmore wrote:
> On Wed Mar 25, 2026 at 6:55 PM CDT, MrXploisLite wrote:
> > Fix checkpatch warning 'please, no space before tabs' in comment blocks.
> > This change removes spaces that precede tab characters in three comment
> > lines within the _TwoOutPipeMapping and _ThreeOutPipeMapping functions.
> >
> > No functional change, only whitespace cleanup to comply with kernel
> > coding style.
> >
> > Signed-off-by: MrXploisLite <arokigaming@gmail.com>
> > ---
> 
> I believe this has been NACKed in the past. This is just changing
> whitespace in a comment, it doesn't really "improve" anything.
> 

Huh.  I can't believe you remember conversations from 2 months ago.  I
had to look it up.  I did NAK this patch, but the reason for that is
the the alignment is wrong before and after the patch.  It should be
something like:

		/*   BK,   BE,   VI,   VO,  BCN,  CMD,  MGT, HIGH, HCCA */
		/*    0,    1,    0,    1,    0,    0,    0,    0,    0 */
		/* 0:ep_0 num, 1:ep_1 num */

So the HCCA column header is over the last zero.

Although, looking at it now, we could just delete the comment.  I think
it was copy and pasted in during development so the author didn't have to
switch windows back and forth when they were implementing the code.  I
don't think it was supposed to be in the released code since it doesn't
add any new information.

pdvobjpriv->Queue2Pipe[0] = pdvobjpriv->RtOutPipe[1];/* VO */
The 1 here matches the VO column.                 ^     ^^

Check that everything is implemented correctly and then just delete
these comments.

regards,
dan carpenter


      reply	other threads:[~2026-03-27  8:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-25 23:55 [PATCH] staging: rtl8723bs: remove spaces before tabs in hal_com.c MrXploisLite
2026-03-26 18:13 ` Ethan Tidmore
2026-03-27  8:03   ` Dan Carpenter [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=acY52ww-3P1bkdsn@stanley.mountain \
    --to=dan.carpenter@linaro.org \
    --cc=arokigaming@gmail.com \
    --cc=ethantidmore06@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-staging@lists.linux.dev \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox