All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philipp Hortmann <philipp.g.hortmann@gmail.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: [PATCH 00/11] staging: rtl8192e: Remove variable priv->rf_chip from driver
Date: Sat, 25 Mar 2023 09:34:56 +0100	[thread overview]
Message-ID: <cover.1679732276.git.philipp.g.hortmann@gmail.com> (raw)

priv->rf_chip is initialized to RF_8256 and never changed. Keep code that
is executed under condition (priv->rf_chip == RF_8256) and remove dead
code including unused variables.

Tested with rtl8192e
Transferred this patch over wlan connection of rtl8192e

Philipp Hortmann (11):
  staging: rtl8192e: Remove priv->rf_chip in _rtl92e_phy_rf_read
  staging: rtl8192e: Remove priv->rf_chip in _rtl92e_phy_rf_write
  staging: rtl8192e: Remove priv->rf_chip in rtl92e_set_tx_power
  staging: rtl8192e: Remove priv->rf_chip in rtl92e_config_phy
  staging: rtl8192e: Remove priv->rf_chip in _rtl92e_set_tx_power_level
  staging: rtl8192e: Remove priv->rf_chip in
    _rtl92e_phy_switch_channel_step
  staging: rtl8192e: Remove priv->rf_chip in
    _rtl92e_set_bw_mode_work_item
  staging: rtl8192e: Remove priv->rf_chip in _rtl92e_set_rf_power_state
  staging: rtl8192e: Remove rf_chip in
    _rtl92e_get_supported_wireless_mode
  staging: rtl8192e: Remove priv->rf_chip in _rtl92e_get_channel_map
  staging: rtl8192e: Remove priv->rf_chip

 .../staging/rtl8192e/rtl8192e/r8192E_dev.c    |   2 -
 .../staging/rtl8192e/rtl8192e/r8192E_phy.c    | 431 ++++++------------
 drivers/staging/rtl8192e/rtl8192e/rtl_core.c  |  23 +-
 drivers/staging/rtl8192e/rtl8192e/rtl_core.h  |  10 -
 4 files changed, 138 insertions(+), 328 deletions(-)

-- 
2.39.2


             reply	other threads:[~2023-03-25  8:35 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-25  8:34 Philipp Hortmann [this message]
2023-03-25  8:35 ` [PATCH 01/11] staging: rtl8192e: Remove priv->rf_chip in _rtl92e_phy_rf_read Philipp Hortmann
2023-03-25  8:35 ` [PATCH 02/11] staging: rtl8192e: Remove priv->rf_chip in _rtl92e_phy_rf_write Philipp Hortmann
2023-03-25  8:35 ` [PATCH 03/11] staging: rtl8192e: Remove priv->rf_chip in rtl92e_set_tx_power Philipp Hortmann
2023-03-25  8:36 ` [PATCH 04/11] staging: rtl8192e: Remove priv->rf_chip in rtl92e_config_phy Philipp Hortmann
2023-03-25  8:36 ` [PATCH 05/11] staging: rtl8192e: Remove priv->rf_chip in _rtl92e_set_tx_power_level Philipp Hortmann
2023-03-25  8:36 ` [PATCH 06/11] staging: rtl8192e: Remove priv->rf_chip in _rtl92e_phy_switch_channel_step Philipp Hortmann
2023-03-25  8:36 ` [PATCH 07/11] staging: rtl8192e: Remove priv->rf_chip in _rtl92e_set_bw_mode_work_item Philipp Hortmann
2023-03-25  8:36 ` [PATCH 08/11] staging: rtl8192e: Remove priv->rf_chip in _rtl92e_set_rf_power_state Philipp Hortmann
2023-03-25  8:36 ` [PATCH 09/11] staging: rtl8192e: Remove rf_chip in _rtl92e_get_supported_wireless_mode Philipp Hortmann
2023-03-25  8:37 ` [PATCH 10/11] staging: rtl8192e: Remove priv->rf_chip in _rtl92e_get_channel_map Philipp Hortmann
2023-03-25  8:37 ` [PATCH 11/11] staging: rtl8192e: Remove priv->rf_chip Philipp Hortmann

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.1679732276.git.philipp.g.hortmann@gmail.com \
    --to=philipp.g.hortmann@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.