Linux kernel staging patches
 help / color / mirror / Atom feed
From: Moksh Panicker <mokshpanicker.7@gmail.com>
To: linux-staging@lists.linux.dev
Cc: gregkh@linuxfoundation.org, dan.carpenter@linaro.org,
	mokshpanicker.7@gmail.com
Subject: [PATCH v5 0/3] staging: rtl8723bs: efuse cleanup and brace fix
Date: Mon, 18 May 2026 18:06:38 +0000	[thread overview]
Message-ID: <20260518180641.44421-1-mokshpanicker.7@gmail.com> (raw)

This series cleans up the rtl8723bs efuse helpers and fixes the
brace/comment spacing issue in rtw_efuse.c. The series has been rechecked,
sent to myself, and compile-tested.

Patch 1 reflows the rtw_efuse_read_1_byte() signature to a single line and
fixes the brace/comment spacing at the end of the function.

Patch 2 adds braces around the else clause in rtw_efuse.c.

Patch 3 reflows the rtw_efuse_one_byte_read() signature to a single line.

Changes from v1 to v2:
1)Reworked the efuse helper signatures to improve 
line length and coding style.
2) Split the cleanup into smaller patches.
3) Fixed the missing brace/comment spacing issue in rtw_efuse.c.

Changes from v2 to v3:
1) Addressed review feedback on the efuse cleanup.
2) Kept the brace fix separate from the helper signature cleanup.
3) Reordered the patches to keep the series easier to review.

Changes from v3 to v4:
1) Folded related cleanup into a more coherent series.
2) Adjusted the patch boundaries.
3) Rechecked the series for style and build correctness.

Changes from v4 to v5:
1) Squashed the redundant efuse brace/comment fix into the final series.
2) Kept the series at 3 patches plus cover letter.
3) Re-ran checkpatch and compile-tested the rtl8723bs build.
4) Addressed Dan Carpenter’s concern about the previous 
version of the brace fix.

Moksh Panicker (3):
  staging: rtl8723bs: reformat rtw_efuse_read_1_byte() signature
  staging: rtl8723bs: add braces to else clause in rtw_efuse.c
  staging: rtl8723bs: reformat rtw_efuse_one_byte_read() signature

 drivers/staging/rtl8723bs/core/rtw_efuse.c | 15 ++++-----------
 1 file changed, 4 insertions(+), 11 deletions(-)

-- 
2.34.1


             reply	other threads:[~2026-05-18 18:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-18 18:06 Moksh Panicker [this message]
2026-05-18 18:06 ` [PATCH v5 1/3] staging: rtl8723bs: reformat rtw_efuse_read_1_byte() signature Moksh Panicker
2026-05-18 18:43   ` Dan Carpenter
2026-05-18 19:11     ` Moksh Panicker
2026-05-18 18:06 ` [PATCH v5 2/3] staging: rtl8723bs: add braces to else clause in rtw_efuse.c Moksh Panicker
2026-05-18 18:06 ` [PATCH v5 3/3] staging: rtl8723bs: reformat rtw_efuse_one_byte_read() signature Moksh Panicker

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=20260518180641.44421-1-mokshpanicker.7@gmail.com \
    --to=mokshpanicker.7@gmail.com \
    --cc=dan.carpenter@linaro.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox