From: Philipp Hortmann <philipp.g.hortmann@gmail.com>
To: Gabriel Tassinari <gabrieldtassinari@gmail.com>,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
~lkcamp/patches@lists.sr.ht
Subject: Re: [PATCH] staging: rtl8192e: Fix parenthesis alignment
Date: Mon, 26 Aug 2024 03:17:40 +0200 [thread overview]
Message-ID: <7ab3f48d-841d-4d61-936c-9e5112a3aaef@gmail.com> (raw)
In-Reply-To: <20240824144345.8873-1-gabrieldtassinari@gmail.com>
On 8/24/24 16:43, Gabriel Tassinari wrote:
> fix parenthesis alignment in _rtl92e_qos_handle_probe_response to
> silence checkpatch warning:
>
> CHECK: Alignment should match open parenthesis
>
> Signed-off-by: Gabriel Tassinari <gabrieldtassinari@gmail.com>
> ---
> drivers/staging/rtl8192e/rtl8192e/rtl_core.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/staging/rtl8192e/rtl8192e/rtl_core.c b/drivers/staging/rtl8192e/rtl8192e/rtl_core.c
> index ad21263e725f..18739583f579 100644
> --- a/drivers/staging/rtl8192e/rtl8192e/rtl_core.c
> +++ b/drivers/staging/rtl8192e/rtl8192e/rtl_core.c
> @@ -322,7 +322,7 @@ static int _rtl92e_qos_handle_probe_response(struct r8192_priv *priv,
>
> if (network->flags & NETWORK_HAS_QOS_MASK) {
> if (active_network &&
> - (network->flags & NETWORK_HAS_QOS_PARAMETERS))
> + (network->flags & NETWORK_HAS_QOS_PARAMETERS))
> network->qos_data.active = network->qos_data.supported;
>
> if ((network->qos_data.active == 1) && (active_network == 1) &&
Hi Gabriel,
Please make your "Subject" line more unique. Consider that we may end up
with having dozen of commits like yours, all of them referring to
different removals and all without the necessary information to tell
what they differ in (except the driver/subsystem). So it would help if
you add the changed file or function to make it more unique.
If you send in a second version of this patch please use a change
history. Description from Dan under:
https://staticthinking.wordpress.com/2022/07/27/how-to-send-a-v2-patch/
Thanks for your support.
Bye Philipp
next prev parent reply other threads:[~2024-08-26 1:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-24 14:43 Gabriel Tassinari
2024-08-26 1:17 ` Philipp Hortmann [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-08-22 0:45 Túlio Fernandes
2024-08-22 0:26 Pedro Orlando
2024-08-22 0:26 [PATCH] staging: rtl8192e: fix " Christian S Lima
2024-08-22 0:25 [PATCH] staging: rtl8192e: Fix " Leonardo Kenji
2024-08-22 0:23 [PATCH] Staging: " Gabriel Maciel Raad
2024-08-22 7:49 ` Greg Kroah-Hartman
2024-08-22 0:23 [PATCH] staging: " Vinicius Peixoto
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=7ab3f48d-841d-4d61-936c-9e5112a3aaef@gmail.com \
--to=philipp.g.hortmann@gmail.com \
--cc=gabrieldtassinari@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®