All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ignacio Peña" <ignacio.pena87@gmail.com>
To: gregkh@linuxfoundation.org, linux-staging@lists.linux.dev
Cc: Ignacio Pena <ignacio.pena87@gmail.com>
Subject: [PATCH 3/3] staging: rtl8723bs: fix indentation in commented code
Date: Wed, 16 Jul 2025 01:36:04 -0400	[thread overview]
Message-ID: <20250716053604.64798-3-ignacio.pena87@gmail.com> (raw)
In-Reply-To: <20250716053604.64798-1-ignacio.pena87@gmail.com>

From: Ignacio Pena <ignacio.pena87@gmail.com>

Fix checkpatch warning by correcting tab indentation in commented
return statement.

Signed-off-by: Ignacio Pena <ignacio.pena87@gmail.com>
---
 drivers/staging/rtl8723bs/core/rtw_cmd.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/staging/rtl8723bs/core/rtw_cmd.c b/drivers/staging/rtl8723bs/core/rtw_cmd.c
index 437934dd2..f02b3b485 100644
--- a/drivers/staging/rtl8723bs/core/rtw_cmd.c
+++ b/drivers/staging/rtl8723bs/core/rtw_cmd.c
@@ -1318,7 +1318,7 @@ u8 rtw_lps_ctrl_wk_cmd(struct adapter *padapter, u8 lps_ctrl_type, u8 enqueue)
        u8 res = _SUCCESS;

        /* if (!pwrctrlpriv->bLeisurePs) */
-       /*      return res; */
+       /*      return res; */

        if (enqueue) {
                ph2c = rtw_zmalloc(sizeof(struct cmd_obj));
-- 
2.39.5

  parent reply	other threads:[~2025-07-16  5:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-16  5:36 [PATCH 1/3] staging: rtl8723bs: fix block comment end markers Ignacio Peña
2025-07-16  5:36 ` [PATCH 2/3] staging: rtl8723bs: add missing blank line after declaration Ignacio Peña
2025-07-16  7:37   ` Greg KH
2025-07-16  5:36 ` Ignacio Peña [this message]
2025-07-16  7:38   ` [PATCH 3/3] staging: rtl8723bs: fix indentation in commented code Greg KH
2025-07-16  7:36 ` [PATCH 1/3] staging: rtl8723bs: fix block comment end markers Greg KH

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=20250716053604.64798-3-ignacio.pena87@gmail.com \
    --to=ignacio.pena87@gmail.com \
    --cc=gregkh@linuxfoundation.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 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.