public inbox for linux-kernel@vger.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 0/7] staging: rtl8192e: Remove entries from struct rtl819x_ops start with .tx_enable
Date: Tue, 21 Feb 2023 21:52:44 +0100	[thread overview]
Message-ID: <cover.1677010997.git.philipp.g.hortmann@gmail.com> (raw)

Remove unnecessary entries from rtl819x_ops and replace them with
function names when required. This increases readability of the code as
the reader does not always need to look up the corresponding function
name. One patch just removes dead code which increases also readability.

Tested with rtl8192e
Transferred this patch over wlan connection of rtl8192e

This patch series requires the this patch series:
"[PATCH 00/11] staging: rtl8192e: Remove entries from struct rtl819x_ops
start with .get_eeprom_size"

Philipp Hortmann (7):
  staging: rtl8192e: Remove entry .tx_enable from struct rtl819x_ops
  staging: rtl8192e: Remove entry .interrupt_re.. from struct
    rtl819x_ops
  staging: rtl8192e: Remove entry .tx_check_stuc.. from struct
    rtl819x_ops
  staging: rtl8192e: Remove entry .rx_check_stuc.. from struct
    rtl819x_ops
  staging: rtl8192e: Remove dead code from struct rtl819x_ops
  staging: rtl8192e: Remove entry .link_change from struct rtl819x_ops
  staging: rtl8192e: Remove entry .nic_type from struct rtl819x_ops

 drivers/staging/rtl8192e/rtl8192e/rtl_core.c | 20 +++++---------------
 drivers/staging/rtl8192e/rtl8192e/rtl_core.h | 12 ------------
 drivers/staging/rtl8192e/rtl8192e/rtl_pci.c  |  6 +++---
 3 files changed, 8 insertions(+), 30 deletions(-)

-- 
2.39.2


             reply	other threads:[~2023-02-21 20:52 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-21 20:52 Philipp Hortmann [this message]
2023-02-21 20:52 ` [PATCH 1/7] staging: rtl8192e: Remove entry .tx_enable from struct rtl819x_ops Philipp Hortmann
2023-02-21 20:53 ` [PATCH 2/7] staging: rtl8192e: Remove entry .interrupt_re.. " Philipp Hortmann
2023-02-21 20:53 ` [PATCH 3/7] staging: rtl8192e: Remove entry .tx_check_stuc.. " Philipp Hortmann
2023-02-21 20:53 ` [PATCH 4/7] staging: rtl8192e: Remove entry .rx_check_stuc.. " Philipp Hortmann
2023-02-21 20:53 ` [PATCH 5/7] staging: rtl8192e: Remove dead code " Philipp Hortmann
2023-02-21 20:53 ` [PATCH 6/7] staging: rtl8192e: Remove entry .link_change " Philipp Hortmann
2023-02-21 20:53 ` [PATCH 7/7] staging: rtl8192e: Remove entry .nic_type " Philipp Hortmann
2023-02-22 13:40   ` Dan Carpenter

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.1677010997.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox