From: Michael Straube <straube.linux@gmail.com>
To: Sevinj Aghayeva <sevinj.aghayeva@gmail.com>,
Pavel Skripkin <paskripkin@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 18:43:26 +0200 [thread overview]
Message-ID: <3e1dfdde-d9f3-9e16-82a6-7b5497981bdd@gmail.com> (raw)
In-Reply-To: <CAMWRUK7g7BqUL1NziBfbc6Epx7G8Xos47sKAtcimDZYmG-hVgA@mail.gmail.com>
On 4/3/22 18:29, Sevinj Aghayeva wrote:
> Ah, I see. You run it on an email file that contains the patch. I
> could reproduce what you saw when I ran checkpatch without any options
> on an email file. But my usual workflow is to modify a file, e.g.
> rtw_mlme.c and then run "checkpatch.pl -f rtw_mlme.c", in which case I
> cannot see the "Alignment should match" error. So it looks like if you
> do not specify -f then checkpatch.pl enables --strict option.
>
Hi Sevinj,
I'm also not a checkpatch expert, but on my system this works without
--strict too. I applied your patch to my local tree and get:
/scripts/checkpatch.pl -f drivers/staging/r8188eu/core/rtw_mlme.c
[snip]
CHECK: Alignment should match open parenthesis
#1638: FILE: drivers/staging/r8188eu/core/rtw_mlme.c:1638:
+ if ((p->PMKIDList[i].bUsed) &&
+ (!memcmp(p->PMKIDList[i].Bssid, bssid,
ETH_ALEN)))
[snip]
You can also run checkpatch on the patch files (without -f).
Then it's easier to see if you introduced new issues.
regards,
Michael
next prev parent reply other threads:[~2022-04-03 16:43 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
2022-04-03 16:29 ` Sevinj Aghayeva
2022-04-03 16:43 ` Michael Straube [this message]
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=3e1dfdde-d9f3-9e16-82a6-7b5497981bdd@gmail.com \
--to=straube.linux@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=outreachy@lists.linux.dev \
--cc=paskripkin@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox