The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: fliegbert2@gmail.com
Cc: linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 5/6] staging: rtl8723bs: Rename camelcase variable dot11AuthAlgrthm_Shared
Date: Tue, 7 Jul 2026 13:02:03 +0200	[thread overview]
Message-ID: <2026070747-certify-gallon-27fe@gregkh> (raw)
In-Reply-To: <537369224ad6d8dff2d045561d0d821469dd125c.1780343502.git.fliegbert2@gmail.com>

On Mon, Jun 01, 2026 at 08:39:57PM +0000, fliegbert2@gmail.com wrote:
> From: Dalvin-Ehinoma Noah Aiguobas <fliegbert2@gmail.com>
> 
> Rename variable dot11AuthAlgrthm_Shared to dot11_auth_algrthm_shared
> to resolve checkpatch.pl CamelCase finding.

It is not a variable, it is a enum :(


  reply	other threads:[~2026-07-07 11:02 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-01 20:39 [PATCH 0/6] staging: rtl8723bs: Rename camelcase enum values dot11AuthAlgrthm_ fliegbert2
2026-06-01 20:39 ` [PATCH 1/6] staging: rtl8723bs: Rename camelcase variable dot11AuthAlgrthm_8021X fliegbert2
2026-07-07 11:02   ` Greg KH
2026-06-01 20:39 ` [PATCH 2/6] staging: rtl8723bs: Replace spaces for tab fliegbert2
2026-06-01 20:39 ` [PATCH 3/6] staging: rtl8723bs: Rename camelcase variable dot11AuthAlgrthm_Open fliegbert2
2026-06-01 20:39 ` [PATCH 4/6] staging: rtl8723bs: Rename camelcase variable dot11AuthAlgrthm_Auto fliegbert2
2026-06-01 20:39 ` [PATCH 5/6] staging: rtl8723bs: Rename camelcase variable dot11AuthAlgrthm_Shared fliegbert2
2026-07-07 11:02   ` Greg KH [this message]
2026-06-01 20:39 ` [PATCH 6/6] staging: rtl8723bs: Rename camelcase variable dot11AuthAlgrthm_WAPI and dot11AuthAlgrthm_MaxNum fliegbert2
2026-07-08 12:15 ` [PATCH v2 0/6] Rename camelcase enum values dot11AuthAlgrthm_ fliegbert2
2026-07-08 12:15   ` [PATCH v2 1/6] staging: rtl8723bs: Rename camelcase enum value dot11AuthAlgrthm_8021X fliegbert2
2026-07-08 12:15   ` [PATCH v2 2/6] staging: rtl8723bs: Replace spaces for tab fliegbert2
2026-07-10  7:52     ` Greg KH
2026-07-08 12:16   ` [PATCH v2 3/6] staging: rtl8723bs: Rename camelcase enum value dot11AuthAlgrthm_Open fliegbert2
2026-07-08 12:16   ` [PATCH v2 4/6] staging: rtl8723bs: Rename camelcase enum value dot11AuthAlgrthm_Auto fliegbert2
2026-07-08 12:16   ` [PATCH v2 5/6] staging: rtl8723bs: Rename camelcase enum value dot11AuthAlgrthm_Shared fliegbert2
2026-07-08 12:16   ` [PATCH v2 6/6] staging: rtl8723bs: Rename camelcase enum values dot11AuthAlgrthm_WAPI and dot11AuthAlgrthm_MaxNum fliegbert2
2026-07-10 10:45 ` [PATCH v3 0/5] Rename camelcase enum values dot11AuthAlgrthm_ fliegbert2
2026-07-10 10:45   ` [PATCH v3 1/5] staging: rtl8723bs: Rename camelcase enum value dot11AuthAlgrthm_8021X fliegbert2
2026-07-10 10:45   ` [PATCH v3 2/5] staging: rtl8723bs: Rename camelcase enum value dot11AuthAlgrthm_Open fliegbert2
2026-07-10 10:45   ` [PATCH v3 3/5] staging: rtl8723bs: Rename camelcase enum value dot11AuthAlgrthm_Auto fliegbert2
2026-07-10 10:45   ` [PATCH v3 4/5] staging: rtl8723bs: Rename camelcase enum value dot11AuthAlgrthm_Shared fliegbert2
2026-07-10 10:45   ` [PATCH v3 5/5] staging: rtl8723bs: Rename camelcase enum values dot11AuthAlgrthm_WAPI and dot11AuthAlgrthm_MaxNum fliegbert2
2026-07-10 14:52   ` [PATCH v3 0/5] Rename camelcase enum values dot11AuthAlgrthm_ Greg KH
2026-07-10 16:20 ` [PATCH v4 0/5] staging: rtl8723bs: " fliegbert2
2026-07-10 16:20   ` [PATCH v4 1/5] staging: rtl8723bs: Rename camelcase enum value dot11AuthAlgrthm_8021X fliegbert2
2026-07-10 16:20   ` [PATCH v4 2/5] staging: rtl8723bs: Rename camelcase enum value dot11AuthAlgrthm_Open fliegbert2
2026-07-10 16:20   ` [PATCH v4 3/5] staging: rtl8723bs: Rename camelcase enum value dot11AuthAlgrthm_Auto fliegbert2
2026-07-10 16:20   ` [PATCH v4 4/5] staging: rtl8723bs: Rename camelcase enum value dot11AuthAlgrthm_Shared fliegbert2
2026-07-10 16:20   ` [PATCH v4 5/5] staging: rtl8723bs: Rename camelcase enum values dot11AuthAlgrthm_WAPI and dot11AuthAlgrthm_MaxNum fliegbert2

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=2026070747-certify-gallon-27fe@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=fliegbert2@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