All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonggeun Park <ndamin221@gmail.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org,
	Jonggeun Park <ndamin221@gmail.com>
Subject: [PATCH 0/2] staging: rtl8723bs: small cleanup of RTL8192C leftovers
Date: Tue, 11 Aug 2026 23:23:53 +0900	[thread overview]
Message-ID: <20260811142355.60533-1-ndamin221@gmail.com> (raw)

Hi,

This is my first patch series to the kernel, and I am glad to
contribute.

The series is a step toward the TODO item "find and remove any code
for other chips that is left over" in drivers/staging/rtl8723bs/TODO:

  - Patch 1 corrects two comments whose referenced file names no
    longer match the files present in the driver.
  - Patch 2 removes two RTL8192C function declarations that have no
    definition or caller anywhere in the kernel tree.

Neither patch introduces a functional change. The driver builds
cleanly with W=1 for CONFIG_RTL8723BS=m.

Thanks,
Jonggeun

Jonggeun Park (2):
  staging: rtl8723bs: fix stale file name references in comments
  staging: rtl8723bs: remove dead RTL8192C function declarations

 drivers/staging/rtl8723bs/hal/rtl8723b_rf6052.c   | 2 +-
 drivers/staging/rtl8723bs/include/rtl8192c_recv.h | 3 ---
 drivers/staging/rtl8723bs/include/rtl8723b_hal.h  | 2 +-
 3 files changed, 2 insertions(+), 5 deletions(-)

-- 
2.43.0


             reply	other threads:[~2026-08-11 14:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-11 14:23 Jonggeun Park [this message]
2026-08-11 14:23 ` [PATCH 1/2] staging: rtl8723bs: fix stale file name references in comments Jonggeun Park
2026-08-11 14:23 ` [PATCH 2/2] staging: rtl8723bs: remove dead RTL8192C function declarations Jonggeun Park

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=20260811142355.60533-1-ndamin221@gmail.com \
    --to=ndamin221@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 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.