From: skhan at linuxfoundation.org (Shuah Khan)
Subject: [Linux-kernel-mentees] [PATCH v2] staging: rtl8723bs: Fix checkpatch.pl warnings
Date: Fri, 26 Apr 2019 12:17:41 -0600 [thread overview]
Message-ID: <2849e876-0e6f-7bad-514b-ec7c8f5637f1@linuxfoundation.org> (raw)
In-Reply-To: <20190426180840.GA5560@bharath12345-Inspiron-5559>
On 4/26/19 12:08 PM, Bharath Vedartham wrote:
> On Fri, Apr 26, 2019 at 11:10:25PM +0530, Vandana BN wrote:
>> fixed below warnings,
>> Comparisons should place the constant on the right side of the test
>> braces {} are not necessary for single statement blocks
>>
>> Signed-off-by: Vandana BN <bnvandana at gmail.com>
>>
>> ------
>> v2- Edited commit message and subject
>> ------
>> ---
>> drivers/staging/rtl8723bs/core/rtw_debug.c | 3 +--
>> 1 file changed, 1 insertion(+), 2 deletions(-)
>>
>> diff --git a/drivers/staging/rtl8723bs/core/rtw_debug.c b/drivers/staging/rtl8723bs/core/rtw_debug.c
>> index 0de1e12a676e..3fb09ad45a67 100644
>> --- a/drivers/staging/rtl8723bs/core/rtw_debug.c
>> +++ b/drivers/staging/rtl8723bs/core/rtw_debug.c
>> @@ -1425,9 +1425,8 @@ int proc_get_btcoex_info(struct seq_file *m, void *v)
>> padapter = (struct adapter *)rtw_netdev_priv(dev);
>>
>> pbuf = rtw_zmalloc(bufsize);
>> - if (NULL == pbuf) {
>> + if (pbuf == NULL)
>> return -ENOMEM;
>> - }
>>
>> rtw_btcoex_DisplayBtCoexInfo(padapter, pbuf, bufsize);
>>
>> --
>> 2.17.1
>>
> Hey!
>
> Your patch subject should briefly describe the changes you are making.
> It should not be very generic like "fix checkpatch.pl warnings" or "fix
> sparse warnings".
>
> A good subject would be:
> "Place constant on the right"
>
> In your changelog, you can mention the fact that this is a checkpatch.pl
> warning. Something like:
> "This patch fixes the checkpatch.pl warning:
> <Whatever the warning was>
> "
>
> Read this before submitting your patch:
> https://kernelnewbies.org/PatchPhilosophy
>
> This is a great place to begin your patches journey!:
> https://kernelnewbies.org/Outreachyfirstpatch
Please don't follow Outreachyfirstpatch instructions - even if
you do, don't send the patch to OutReachy mailing list and this
will be very confusing!!
You should follow the instructions on
https://wiki.linuxfoundation.org/lkmp to send patches.
>
> And also did you send this to the appropriate mailing lists?
This is fine - the first patch can come just to
linux-kernel-mentees at lists.linuxfoundation.org
>
> Use ./scripts/get_maintainer.pl to get the maintainer and mailing list
> to send this patch to. You ll be sending your patch to Greg again :p as
> he maintains the staging branch.
>
Greg is on the cc.
thanks,
-- Shuah
WARNING: multiple messages have this Message-ID (diff)
From: skhan@linuxfoundation.org (Shuah Khan)
Subject: [Linux-kernel-mentees] [PATCH v2] staging: rtl8723bs: Fix checkpatch.pl warnings
Date: Fri, 26 Apr 2019 12:17:41 -0600 [thread overview]
Message-ID: <2849e876-0e6f-7bad-514b-ec7c8f5637f1@linuxfoundation.org> (raw)
Message-ID: <20190426181741.jbeDq21C7PMQmgE29jAqk5qwDbgAEi9ocQZ8PKQjIoE@z> (raw)
In-Reply-To: <20190426180840.GA5560@bharath12345-Inspiron-5559>
On 4/26/19 12:08 PM, Bharath Vedartham wrote:
> On Fri, Apr 26, 2019 at 11:10:25PM +0530, Vandana BN wrote:
>> fixed below warnings,
>> Comparisons should place the constant on the right side of the test
>> braces {} are not necessary for single statement blocks
>>
>> Signed-off-by: Vandana BN <bnvandana at gmail.com>
>>
>> ------
>> v2- Edited commit message and subject
>> ------
>> ---
>> drivers/staging/rtl8723bs/core/rtw_debug.c | 3 +--
>> 1 file changed, 1 insertion(+), 2 deletions(-)
>>
>> diff --git a/drivers/staging/rtl8723bs/core/rtw_debug.c b/drivers/staging/rtl8723bs/core/rtw_debug.c
>> index 0de1e12a676e..3fb09ad45a67 100644
>> --- a/drivers/staging/rtl8723bs/core/rtw_debug.c
>> +++ b/drivers/staging/rtl8723bs/core/rtw_debug.c
>> @@ -1425,9 +1425,8 @@ int proc_get_btcoex_info(struct seq_file *m, void *v)
>> padapter = (struct adapter *)rtw_netdev_priv(dev);
>>
>> pbuf = rtw_zmalloc(bufsize);
>> - if (NULL == pbuf) {
>> + if (pbuf == NULL)
>> return -ENOMEM;
>> - }
>>
>> rtw_btcoex_DisplayBtCoexInfo(padapter, pbuf, bufsize);
>>
>> --
>> 2.17.1
>>
> Hey!
>
> Your patch subject should briefly describe the changes you are making.
> It should not be very generic like "fix checkpatch.pl warnings" or "fix
> sparse warnings".
>
> A good subject would be:
> "Place constant on the right"
>
> In your changelog, you can mention the fact that this is a checkpatch.pl
> warning. Something like:
> "This patch fixes the checkpatch.pl warning:
> <Whatever the warning was>
> "
>
> Read this before submitting your patch:
> https://kernelnewbies.org/PatchPhilosophy
>
> This is a great place to begin your patches journey!:
> https://kernelnewbies.org/Outreachyfirstpatch
Please don't follow Outreachyfirstpatch instructions - even if
you do, don't send the patch to OutReachy mailing list and this
will be very confusing!!
You should follow the instructions on
https://wiki.linuxfoundation.org/lkmp to send patches.
>
> And also did you send this to the appropriate mailing lists?
This is fine - the first patch can come just to
linux-kernel-mentees at lists.linuxfoundation.org
>
> Use ./scripts/get_maintainer.pl to get the maintainer and mailing list
> to send this patch to. You ll be sending your patch to Greg again :p as
> he maintains the staging branch.
>
Greg is on the cc.
thanks,
-- Shuah
next prev parent reply other threads:[~2019-04-26 18:17 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-26 13:12 [Linux-kernel-mentees] [PATCH] Fix checkpatch.pl warnings bnvandana
2019-04-26 13:12 ` Vandana BN
2019-04-26 13:49 ` skhan
2019-04-26 13:49 ` Shuah Khan
2019-04-26 17:46 ` bnvandana
2019-04-26 17:46 ` bnva
2019-04-26 17:40 ` [Linux-kernel-mentees] [PATCH v2] staging: rtl8723bs: " bnvandana
2019-04-26 17:40 ` Vandana BN
2019-04-26 18:08 ` linux.bhar
2019-04-26 18:08 ` Bharath Vedartham
2019-04-26 18:17 ` skhan [this message]
2019-04-26 18:17 ` Shuah Khan
2019-04-26 18:54 ` skhan
2019-04-26 18:54 ` Shuah Khan
2019-04-27 5:50 ` [Linux-kernel-mentees] [PATCH v3] " bnvandana
2019-04-27 5:50 ` Vandana BN
2019-04-27 6:31 ` gregkh
2019-04-27 6:31 ` Greg KH
2019-04-27 7:24 ` bnvandana
2019-04-27 7:24 ` Vandana BN
2019-04-27 7:31 ` gregkh
2019-04-27 7:31 ` Greg KH
2019-04-27 7:40 ` [Linux-kernel-mentees] [PATCH v4] " bnvandana
2019-04-27 7:40 ` Vandana BN
2019-04-29 16:00 ` bnvandana
2019-04-29 16:00 ` Vandana BN
2019-04-29 16:00 ` [Linux-kernel-mentees] " Vandana BN
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=2849e876-0e6f-7bad-514b-ec7c8f5637f1@linuxfoundation.org \
--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.