All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Skripkin <paskripkin@gmail.com>
To: Sevinj Aghayeva <sevinj.aghayeva@gmail.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org,
	outreachy@lists.linux.dev
Subject: Re: [PATCH] staging: r8188eu: simplify control flow
Date: Sun, 3 Apr 2022 19:16:10 +0300	[thread overview]
Message-ID: <4ccc9ac3-c542-cd32-0cbb-7cdabbf0dbf9@gmail.com> (raw)
In-Reply-To: <CAMWRUK6K77KpRkCkruL=RQcmA1opbvapyPJOA-EFpYdXxY8ujQ@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 998 bytes --]

Hi Sevinj,

On 4/3/22 19:12, Sevinj Aghayeva wrote:
>>
>> Looks good, but let's not introduce new checkpatch issue:
>>
>> CHECK: Alignment should match open parenthesis
>> #62: FILE: drivers/staging/r8188eu/core/rtw_mlme.c:1645:
>> +               if ((p->PMKIDList[i].bUsed) &&
>> +                               (!memcmp(p->PMKIDList[i].Bssid, bssid, ETH_ALEN)))
> 
> Thanks for catching this. I wasn't seeing this in my checkpatch
> output, and after some digging, I could reproduce it with --strict
> option. I think the tutorial at
> https://kernelnewbies.org/PatchPhilosophy doesn't mention this option,
> so perhaps we should update it?!
> 

To be honest, I am not checkpatch expert, but checkpatch on my PC shows 
this warning w/o any additional options:

└──$ ./scripts/checkpatch.pl 
./20220403_sevinj_aghayeva_staging_r8188eu_simplify_control_flow.mbx | 
rg Alignment
CHECK: Alignment should match open parenthesis





With regards,
Pavel Skripkin

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]

  reply	other threads:[~2022-04-03 16:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-03 15:51 [PATCH] staging: r8188eu: simplify control flow Sevinj Aghayeva
2022-04-03 15:59 ` Pavel Skripkin
2022-04-03 16:12   ` Sevinj Aghayeva
2022-04-03 16:16     ` Pavel Skripkin [this message]
2022-04-03 16:29       ` Sevinj Aghayeva
2022-04-03 16:43         ` Michael Straube
2022-04-03 16:59           ` Sevinj Aghayeva

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=4ccc9ac3-c542-cd32-0cbb-7cdabbf0dbf9@gmail.com \
    --to=paskripkin@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-staging@lists.linux.dev \
    --cc=outreachy@lists.linux.dev \
    --cc=sevinj.aghayeva@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 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.