public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Linus Probert <linus.probert@gmail.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org,
	Linus Probert <linus.probert@gmail.com>
Subject: [PATCH v3 7/7] staging: rtl8723bs: remove space before tab
Date: Tue, 31 Mar 2026 17:53:18 +0200	[thread overview]
Message-ID: <20260331155318.185117-8-linus.probert@gmail.com> (raw)
In-Reply-To: <20260331155318.185117-1-linus.probert@gmail.com>

Removes a space before tab according to kernel code style.
Discovered using the checkpatch.pl tool.

Signed-off-by: Linus Probert <linus.probert@gmail.com>
---
 drivers/staging/rtl8723bs/include/rtw_efuse.h | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/staging/rtl8723bs/include/rtw_efuse.h b/drivers/staging/rtl8723bs/include/rtw_efuse.h
index 4e8980d86965..808ba94a5998 100644
--- a/drivers/staging/rtl8723bs/include/rtw_efuse.h
+++ b/drivers/staging/rtl8723bs/include/rtw_efuse.h
@@ -31,7 +31,7 @@ enum {
 #define		EFUSE_REPEAT_THRESHOLD_			3
 
 /*  */
-/* 	The following is for BT Efuse definition */
+/*	The following is for BT Efuse definition */
 /*  */
 #define		EFUSE_BT_MAX_MAP_LEN		1024
 #define		EFUSE_MAX_BANK			4
-- 
2.53.0


  parent reply	other threads:[~2026-03-31 15:53 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-31 15:53 [PATCH v3 0/7] rename/remove functions and code style cleanup Linus Probert
2026-03-31 15:53 ` [PATCH v3 1/7] staging: rtl8723bs: rename global function to snake_case Linus Probert
2026-03-31 15:53 ` [PATCH v3 2/7] " Linus Probert
2026-03-31 15:53 ` [PATCH v3 3/7] " Linus Probert
2026-03-31 15:53 ` [PATCH v3 4/7] " Linus Probert
2026-03-31 15:53 ` [PATCH v3 5/7] " Linus Probert
2026-03-31 15:53 ` [PATCH v3 6/7] staging: rtl8723bs: remove unused global functions Linus Probert
2026-03-31 15:53 ` Linus Probert [this message]
2026-04-01  1:39 ` [PATCH v3 0/7] rename/remove functions and code style cleanup Ethan Tidmore
2026-04-01 10:05 ` Greg Kroah-Hartman

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=20260331155318.185117-8-linus.probert@gmail.com \
    --to=linus.probert@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