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/5] staging: rtl8192e: Remove c files dot11d.c/.h
Date: Fri, 8 Dec 2023 19:19:23 +0100	[thread overview]
Message-ID: <cover.1701989555.git.philipp.g.hortmann@gmail.com> (raw)

Remove function rtllib_update_active_chan_map() as "active_channel_map"
and "channel_map" have the same content. Content of "channel_map" does
not change.

Tested with rtl8192e (WLL6130-D99) in Mode n (12.5 MB/s)
Transferred this patch over wlan connection of rtl8192e.

Used the following code for testing:
struct rt_dot11d_info *ph = priv->rtllib->dot11d_info;
for (i = 1; i <= 13; i++){
	printk("priv->rtllib->active_channel_map)  [%d] %d\n", i, priv->rtllib->active_channel_map[i]);
	printk("priv->rtllib->dot11d_info->chan_map[%d] %d\n", i, ph->channel_map[i]);
}
Log:
[ 1141.288386] priv->rtllib->active_channel_map)  [1] 1
[ 1141.288393] priv->rtllib->dot11d_info->chan_map[1] 1
[ 1141.288395] priv->rtllib->active_channel_map)  [2] 1
[ 1141.288396] priv->rtllib->dot11d_info->chan_map[2] 1
...
[ 1141.288426] priv->rtllib->active_channel_map)  [11] 1
[ 1141.288428] priv->rtllib->dot11d_info->chan_map[11] 1
[ 1141.288429] priv->rtllib->active_channel_map)  [12] 2
[ 1141.288431] priv->rtllib->dot11d_info->chan_map[12] 2
[ 1141.288433] priv->rtllib->active_channel_map)  [13] 2
[ 1141.288434] priv->rtllib->dot11d_info->chan_map[13] 2

Philipp Hortmann (5):
  staging: rtl8192e: Remove function rtllib_update_active_chan_map()
  staging: rtl8192e: Remove variable channel_map
  staging: rtl8192e: Remove variable dot11d_info
  staging: rtl8192e: Remove function dot11d_channel_map()
  staging: rtl8192e: Remove files dot11d.c and dot11d.h

 drivers/staging/rtl8192e/Makefile            |  1 -
 drivers/staging/rtl8192e/dot11d.c            | 29 -------------------
 drivers/staging/rtl8192e/dot11d.h            | 30 --------------------
 drivers/staging/rtl8192e/rtl8192e/rtl_core.c |  1 -
 drivers/staging/rtl8192e/rtl8192e/rtl_core.h |  2 --
 drivers/staging/rtl8192e/rtllib.h            |  1 -
 drivers/staging/rtl8192e/rtllib_rx.c         |  1 -
 drivers/staging/rtl8192e/rtllib_softmac.c    | 19 -------------
 drivers/staging/rtl8192e/rtllib_softmac_wx.c |  1 -
 9 files changed, 85 deletions(-)
 delete mode 100644 drivers/staging/rtl8192e/dot11d.c
 delete mode 100644 drivers/staging/rtl8192e/dot11d.h

-- 
2.43.0


             reply	other threads:[~2023-12-08 18:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-08 18:19 Philipp Hortmann [this message]
2023-12-08 18:19 ` [PATCH 1/5] staging: rtl8192e: Remove function rtllib_update_active_chan_map() Philipp Hortmann
2023-12-08 18:19 ` [PATCH 2/5] staging: rtl8192e: Remove variable channel_map Philipp Hortmann
2023-12-08 18:19 ` [PATCH 3/5] staging: rtl8192e: Remove variable dot11d_info Philipp Hortmann
2023-12-08 18:19 ` [PATCH 4/5] staging: rtl8192e: Remove function dot11d_channel_map() Philipp Hortmann
2023-12-08 18:20 ` [PATCH 5/5] staging: rtl8192e: Remove files dot11d.c and dot11d.h 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.1701989555.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