From: Nam Cao <namcao@linutronix.de>
To: Alien Wesley <alienwesley51@gmail.com>
Cc: gregkh@linuxfoundation.org, linux-staging@lists.linux.dev,
linux-kernel@vger.kernel.org, ~lkcamp/patches@lists.sr.ht
Subject: Re: [PATCH v3] staging: rtl8192e: Fix multiple assignments in rtl_wx.c:529
Date: Mon, 26 Aug 2024 20:20:29 +0200 [thread overview]
Message-ID: <20240826182029.ZFtqcPCP@linutronix.de> (raw)
In-Reply-To: <20240826162804.18996-1-alienwesley51@gmail.com>
On Mon, Aug 26, 2024 at 01:28:04PM -0300, Alien Wesley wrote:
> Separated assignments for pairwise_key_type and group_key_type
> in order to silence the following checkpatch warning.
>
> CHECK: multiple assignments should be avoided.
>
> Signed-off-by: Alien Wesley <alienwesley51@gmail.com>
> ---
> v3: Fix typo in commit message.
> v2: Removed two spaces in front of "=".
> ---
> drivers/staging/rtl8192e/rtl8192e/rtl_wx.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/staging/rtl8192e/rtl8192e/rtl_wx.c b/drivers/staging/rtl8192e/rtl8192e/rtl_wx.c
> index 47f1adf30ab4..67c4793e0fc1 100644
> --- a/drivers/staging/rtl8192e/rtl8192e/rtl_wx.c
> +++ b/drivers/staging/rtl8192e/rtl8192e/rtl_wx.c
> @@ -526,7 +526,7 @@ static int _rtl92e_wx_set_enc(struct net_device *dev,
> mutex_unlock(&priv->wx_mutex);
>
> if (wrqu->encoding.flags & IW_ENCODE_DISABLED) {
> - ieee->pairwise_key_type = KEY_TYPE_NA;
> + ieee->pairwise_key_type = KEY_TYPE_NA;
I was completely confused, because the desscription says "Fix multiple
assignments", yet I only see a whitespace fix.
So I looked at v1, and it makes sense, you are sending this as a follow-up
fix for a double-space issue that you added in v1.
Instead of doing this, please just squash your v1 and v3 patches together
and send it as v4. This v3 patch doesn't make sense on its own.
Best regards,
Nam
prev parent reply other threads:[~2024-08-26 18:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-26 16:28 Alien Wesley
2024-08-26 18:20 ` Nam Cao [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=20240826182029.ZFtqcPCP@linutronix.de \
--to=namcao@linutronix.de \
--cc=alienwesley51@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=~lkcamp/patches@lists.sr.ht \
/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
all inboxes | Powered by JetHome®