public inbox for linux-staging@lists.linux.dev
 help / color / mirror / Atom feed
From: "Ethan Tidmore" <ethantidmore06@gmail.com>
To: "Linus Probert" <linus.probert@gmail.com>,
	"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>
Cc: <linux-staging@lists.linux.dev>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v4 4/7] staging: rtl8723bs: EFUSE_ShadowMapUpdate() -> rtw_shadow_map_update()
Date: Wed, 01 Apr 2026 22:01:11 -0500	[thread overview]
Message-ID: <DHIC17WZQBN1.33XD5KDW2O0E2@gmail.com> (raw)
In-Reply-To: <20260401190814.216333-5-linus.probert@gmail.com>

On Wed Apr 1, 2026 at 2:08 PM CDT, Linus Probert wrote:
> Renames EFUSE_ShadowMapUpdate to rtw_shadow_map_update in order to
> conform to kernel code style.

Your changes show rtw_efuse_shadow_map_update() but, your commit says it
changes to rtw_shadow_map_update().

Thanks,

ET

  reply	other threads:[~2026-04-02  3:01 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-01 19:08 [PATCH v4 0/7] staging: rtl8723bs: rename/remove functions Linus Probert
2026-04-01 19:08 ` [PATCH v4 1/7] staging: rtl8723bs: rename global function Efuse_CalculateWordCnts Linus Probert
2026-04-01 19:08 ` [PATCH v4 2/7] staging: rtl8723bs: efuse_OneByteRead() -> rtw_efuse_one_byte_read() Linus Probert
2026-04-01 19:08 ` [PATCH v4 3/7] staging: rtl8723bs: rename EFUSE_Read1Byte() to rtw_efuse_read_1_byte() Linus Probert
2026-04-01 19:08 ` [PATCH v4 4/7] staging: rtl8723bs: EFUSE_ShadowMapUpdate() -> rtw_shadow_map_update() Linus Probert
2026-04-02  3:01   ` Ethan Tidmore [this message]
2026-04-01 19:08 ` [PATCH v4 5/7] staging: rtl8723bs: rename EFUSE_ShadowRead() to rtw_efuse_shadow_read() Linus Probert
2026-04-01 19:08 ` [PATCH v4 6/7] staging: rtl8723bs: remove unused global functions Linus Probert
2026-04-02  3:04   ` Ethan Tidmore
2026-04-01 19:08 ` [PATCH v4 7/7] staging: rtl8723bs: remove space before tab Linus Probert

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=DHIC17WZQBN1.33XD5KDW2O0E2@gmail.com \
    --to=ethantidmore06@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linus.probert@gmail.com \
    --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