From: Philipp Hortmann <philipp.g.hortmann@gmail.com>
To: Aaron Parfitt <aaronparfitt123@gmail.com>, gregkh@linuxfoundation.org
Cc: linux-kernel@vger.kernel.org, linux-staging@lists.linux.dev
Subject: Re: [PATCH] Staging: rtl8192e: rtl819x_HTProc: Removed braces from single statement block
Date: Thu, 15 Feb 2024 10:32:41 +0100 [thread overview]
Message-ID: <817953da-12ee-4720-aef1-725d07c2704e@gmail.com> (raw)
In-Reply-To: <20240213074649.18158-1-aaronparfitt123@gmail.com>
Hi Aaron,
looks OK but can we make the subject more unique. Maybe like this:
[PATCH] Staging: rtl8192e: Removed braces from single statement block in
ht_on_assoc_rsp
Or is this getting to long?
I propose the description to be like:
Remove braces from single statement blocks to clear checkpatch warning.
If you change this you need to make a v2 with changelog.
Bye Philipp
On 13.02.24 08:46, Aaron Parfitt wrote:
> Fixed code style issue
>
> Signed-off-by: Aaron Parfitt <aaronparfitt123@gmail.com>
> ---
> drivers/staging/rtl8192e/rtl819x_HTProc.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/staging/rtl8192e/rtl819x_HTProc.c b/drivers/staging/rtl8192e/rtl819x_HTProc.c
> index 6d0912f90198..49b882c363bf 100644
> --- a/drivers/staging/rtl8192e/rtl819x_HTProc.c
> +++ b/drivers/staging/rtl8192e/rtl819x_HTProc.c
> @@ -480,9 +480,9 @@ void ht_on_assoc_rsp(struct rtllib_device *ieee)
> }
>
> ht_info->current_mpdu_density = pPeerHTCap->MPDUDensity;
> - if (ht_info->iot_action & HT_IOT_ACT_TX_USE_AMSDU_8K) {
> + if (ht_info->iot_action & HT_IOT_ACT_TX_USE_AMSDU_8K)
> ht_info->current_ampdu_enable = false;
> - }
> +
> ht_info->cur_rx_reorder_enable = 1;
>
> if (pPeerHTCap->MCS[0] == 0)
prev parent reply other threads:[~2024-02-15 9:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-13 7:46 [PATCH] Staging: rtl8192e: rtl819x_HTProc: Removed braces from single statement block Aaron Parfitt
2024-02-15 9:32 ` Philipp Hortmann [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=817953da-12ee-4720-aef1-725d07c2704e@gmail.com \
--to=philipp.g.hortmann@gmail.com \
--cc=aaronparfitt123@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
/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