public inbox for linux-staging@lists.linux.dev
 help / color / mirror / Atom feed
From: Shuah Khan <skhan@linuxfoundation.org>
To: Prithvi <activprithvi@gmail.com>,
	Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: gregkh@linuxfoundation.org, abrahamadekunle50@gmail.com,
	straube.linux@gmail.com, b9788213@gmail.com,
	ethantidmore06@gmail.com, dan.carpenter@linaro.org,
	weibu@redadmin.org, knavaneeth786@gmail.com,
	ignacio.pena87@gmail.com, dharanitharan725@gmail.com,
	lukagejak5@gmail.com, samasth.norway.ananda@oracle.com,
	karanja99erick@gmail.com, s9430939@naver.com,
	suunj1331@gmail.com, ysinghcin@gmail.com,
	linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org,
	linux-kernel-mentees@lists.linux.dev,
	david.hunter.linux@gmail.com, khalid@kernel.org,
	Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [PATCH v2] staging: rtl8723bs: fix constant on left side of test checkpatch warnings
Date: Tue, 24 Mar 2026 11:41:40 -0600	[thread overview]
Message-ID: <656d3bf5-8d97-454e-9691-540cdb79dab4@linuxfoundation.org> (raw)
In-Reply-To: <20260324160229.f46h25ebd2mxcfiq@inspiron>

On 3/24/26 10:02, Prithvi wrote:
> On Tue, Mar 24, 2026 at 04:05:51PM +0200, Andy Shevchenko wrote:
>> On Tue, Mar 24, 2026 at 07:25:51PM +0530, Prithvi wrote:
>>> Sure. Also can you please guide if any testing would be required for these
>>> changes, or I can directly send the v3 patch?
>>
>> It's implied that the author of the patch each time before submission (either
>> a new version of the existing patch or a new patch in general) is tested and
>> validated it.

+1

>>
>> -- 
>> With Best Regards,
>> Andy Shevchenko
>>
>>
> 
> Understood. I agree that patch must be tested and validated every time.
> 
> To be transparent, I do not have access to the physical Realtek hardware,
> so I am unable to perform runtime testing. However, for this v3, I have
> performed compile testing and ensured that the module builds correctly.
> Will this be acceptable for this patch?

No -  Hmm. Aren't you part of Fall mentorship program?

We discussed this several times during the program that when someone
sends a patch, it is implied that they tested the patch. Compile
testing isn't sufficient. The changes in this patch not trivial spelling
fixes in comments either.

  
-	if (1 <= channel && channel <= 14) {
+	if (channel >= 1 && channel <= 14) {

I picked just one and there are more like this one.

These aren't just moving the constant lies to the right side of the test,
they change logic and in some cases removing the code and the change log
doesn't say anything about that.

Did you look into if this conditional can just go away?

-	if (0x00 == PathAOK) {
-	}


I am not the maintainer for this, but as your mentor this isn't acceptable.
I wouldn't take this patch unless these changes are tested on the device.

thanks,
-- Shuah

  reply	other threads:[~2026-03-24 17:41 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-23 16:29 [PATCH v2] staging: rtl8723bs: fix constant on left side of test checkpatch warnings Prithvi Tambewagh
2026-03-23 16:42 ` Andy Shevchenko
2026-03-24 13:02   ` Prithvi
2026-03-24 13:43     ` Andy Shevchenko
2026-03-24 13:55       ` Prithvi
2026-03-24 14:05         ` Andy Shevchenko
2026-03-24 16:02           ` Prithvi
2026-03-24 17:41             ` Shuah Khan [this message]
2026-03-25  7:22               ` Dan Carpenter
2026-03-25 17:57                 ` Shuah Khan
2026-03-25 21:34                   ` Dan Carpenter
2026-03-25 22:22                     ` Shuah Khan
2026-03-28 17:47 ` Prithvi

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=656d3bf5-8d97-454e-9691-540cdb79dab4@linuxfoundation.org \
    --to=skhan@linuxfoundation.org \
    --cc=abrahamadekunle50@gmail.com \
    --cc=activprithvi@gmail.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=b9788213@gmail.com \
    --cc=dan.carpenter@linaro.org \
    --cc=david.hunter.linux@gmail.com \
    --cc=dharanitharan725@gmail.com \
    --cc=ethantidmore06@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=ignacio.pena87@gmail.com \
    --cc=karanja99erick@gmail.com \
    --cc=khalid@kernel.org \
    --cc=knavaneeth786@gmail.com \
    --cc=linux-kernel-mentees@lists.linux.dev \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-staging@lists.linux.dev \
    --cc=lukagejak5@gmail.com \
    --cc=s9430939@naver.com \
    --cc=samasth.norway.ananda@oracle.com \
    --cc=straube.linux@gmail.com \
    --cc=suunj1331@gmail.com \
    --cc=weibu@redadmin.org \
    --cc=ysinghcin@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox