linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Fabio Aiuto <fabioaiuto83@gmail.com>
To: gregkh@linuxfoundation.org
Cc: dan.carpenter@oracle.com, hdegoede@redhat.com,
	Larry.Finger@lwfinger.net, linux-staging@lists.linux.dev,
	linux-kernel@vger.kernel.org
Subject: [PATCH v2 00/10] staging: rtl8723bs: add get_channel implementation
Date: Sat, 17 Jul 2021 16:56:41 +0200	[thread overview]
Message-ID: <cover.1626533647.git.fabioaiuto83@gmail.com> (raw)

This patchset adds cfg80211 get_channel implementation.
One of the benefits is having displayed channel info
in iw dev output.

Done some code cleaning as well.

Tested-on: Lenovo Ideapad MiiX-300-10IBY

Fabio Aiuto (10):
  staging: rtl8723bs: add get_channel cfg80211 implementation
  staging: rtl8723bs: convert IsSupportedHT to snake_case
  staging: rtl8723bs: fix camel case issue
  staging: rtl8723bs: fix camel case name in macro IsLegacyOnly()
  staging: rtl8723bs: fix camel case in argument of macro is_legacy_only
  staging: rtl8723bs: fix camel case name in macro IsSupported24G
  staging: rtl8723bs: fix post-commit camel case issues
  staging: rtl8723bs: remove unused macros in include/ieee80211.h
  staging: rtl8723bs: fix camel case name in macro IsSupportedTxCCK
  staging: rtl8723bs: fix camel case argument name in macro
    is_supported_tx_cck

 drivers/staging/rtl8723bs/core/rtw_ap.c       |  2 +-
 .../staging/rtl8723bs/core/rtw_ioctl_set.c    |  2 +-
 drivers/staging/rtl8723bs/core/rtw_mlme_ext.c |  2 +-
 .../staging/rtl8723bs/core/rtw_wlan_util.c    |  4 +-
 drivers/staging/rtl8723bs/hal/hal_btcoex.c    |  2 +-
 drivers/staging/rtl8723bs/hal/hal_com.c       |  4 +-
 drivers/staging/rtl8723bs/include/ieee80211.h | 16 ++----
 .../staging/rtl8723bs/os_dep/ioctl_cfg80211.c | 53 ++++++++++++++++++-
 8 files changed, 64 insertions(+), 21 deletions(-)

-- 
2.20.1


             reply	other threads:[~2021-07-17 14:57 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-17 14:56 Fabio Aiuto [this message]
2021-07-17 14:56 ` [PATCH v2 01/10] staging: rtl8723bs: add get_channel cfg80211 implementation Fabio Aiuto
2021-07-17 14:56 ` [PATCH v2 02/10] staging: rtl8723bs: convert IsSupportedHT to snake_case Fabio Aiuto
2021-07-17 14:56 ` [PATCH v2 03/10] staging: rtl8723bs: fix camel case issue Fabio Aiuto
2021-07-17 14:56 ` [PATCH v2 04/10] staging: rtl8723bs: fix camel case name in macro IsLegacyOnly() Fabio Aiuto
2021-07-17 14:56 ` [PATCH v2 05/10] staging: rtl8723bs: fix camel case in argument of macro is_legacy_only Fabio Aiuto
2021-07-17 14:56 ` [PATCH v2 06/10] staging: rtl8723bs: fix camel case name in macro IsSupported24G Fabio Aiuto
2021-07-17 14:56 ` [PATCH v2 07/10] staging: rtl8723bs: fix post-commit camel case issues Fabio Aiuto
2021-07-17 14:56 ` [PATCH v2 08/10] staging: rtl8723bs: remove unused macros in include/ieee80211.h Fabio Aiuto
2021-07-17 14:56 ` [PATCH v2 09/10] staging: rtl8723bs: fix camel case name in macro IsSupportedTxCCK Fabio Aiuto
2021-07-17 14:56 ` [PATCH v2 10/10] staging: rtl8723bs: fix camel case argument name in macro is_supported_tx_cck Fabio Aiuto

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=cover.1626533647.git.fabioaiuto83@gmail.com \
    --to=fabioaiuto83@gmail.com \
    --cc=Larry.Finger@lwfinger.net \
    --cc=dan.carpenter@oracle.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=hdegoede@redhat.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;
as well as URLs for NNTP newsgroup(s).