From: Phillip Potter <phil@philpotter.co.uk>
To: gregkh@linuxfoundation.org
Cc: Larry.Finger@lwfinger.net, straube.linux@gmail.com,
kaixuxia@tencent.com, linux-staging@lists.linux.dev,
linux-kernel@vger.kernel.org, liushixin2@huawei.com,
unixbhaskar@gmail.com, gustavoars@kernel.org, martin@kaiser.cx,
bkkarthik@pesu.pes.edu, dan.carpenter@oracle.com
Subject: [PATCH 0/6] staging: rtl8188eu: remove hal/odm_debug.h
Date: Fri, 11 Jun 2021 01:24:58 +0100 [thread overview]
Message-ID: <20210611002504.166405-1-phil@philpotter.co.uk> (raw)
This series removes hal/odm_debug.h, which contains various preprocessor
definitions, as well as an unwieldy ODM_RT_TRACE macro which is not best
practice. It also removes all uses of this macro, and the associated
fields in struct odm_dm_struct which are only used by this macro.
This makes the code cleaner, thus moving it closer to getting out of
staging.
Phillip Potter (6):
staging: rtl8188eu: remove ODM_RT_TRACE calls from hal/phy.c
staging: rtl8188eu: remove ODM_RT_TRACE calls from
hal/hal8188e_rate_adaptive.c
staging: rtl8188eu: remove ODM_RT_TRACE calls from hal/odm_rtl8188e.c
staging: rtl8188eu: remove ODM_RT_TRACE calls from hal/odm.c
staging: rtl8188eu: remove DebugComponents/DebugLevel from
odm_dm_struct
staging: rtl8188eu: remove include/odm_debug.h
.../rtl8188eu/hal/hal8188e_rate_adaptive.c | 123 +-------------
drivers/staging/rtl8188eu/hal/odm.c | 150 ++----------------
drivers/staging/rtl8188eu/hal/odm_rtl8188e.c | 6 -
drivers/staging/rtl8188eu/hal/phy.c | 38 +----
drivers/staging/rtl8188eu/hal/rtl8188e_dm.c | 2 -
drivers/staging/rtl8188eu/hal/usb_halinit.c | 5 -
drivers/staging/rtl8188eu/include/odm.h | 2 -
drivers/staging/rtl8188eu/include/odm_debug.h | 83 ----------
.../staging/rtl8188eu/include/odm_precomp.h | 4 -
9 files changed, 14 insertions(+), 399 deletions(-)
delete mode 100644 drivers/staging/rtl8188eu/include/odm_debug.h
--
2.30.2
next reply other threads:[~2021-06-11 0:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-11 0:24 Phillip Potter [this message]
2021-06-11 0:24 ` [PATCH 1/6] staging: rtl8188eu: remove ODM_RT_TRACE calls from hal/phy.c Phillip Potter
2021-06-11 0:25 ` [PATCH 2/6] staging: rtl8188eu: remove ODM_RT_TRACE calls from hal/hal8188e_rate_adaptive.c Phillip Potter
2021-06-11 0:25 ` [PATCH 3/6] staging: rtl8188eu: remove ODM_RT_TRACE calls from hal/odm_rtl8188e.c Phillip Potter
2021-06-11 0:25 ` [PATCH 4/6] staging: rtl8188eu: remove ODM_RT_TRACE calls from hal/odm.c Phillip Potter
2021-06-11 0:25 ` [PATCH 5/6] staging: rtl8188eu: remove DebugComponents/DebugLevel from odm_dm_struct Phillip Potter
2021-06-11 0:25 ` [PATCH 6/6] staging: rtl8188eu: remove include/odm_debug.h Phillip Potter
2021-06-11 9:08 ` [PATCH 5/6] staging: rtl8188eu: remove DebugComponents/DebugLevel from odm_dm_struct Dan Carpenter
2021-06-12 17:37 ` Phillip Potter
2021-06-11 9:10 ` [PATCH 0/6] staging: rtl8188eu: remove hal/odm_debug.h Dan Carpenter
2021-06-11 15:35 ` Martin Kaiser
2021-06-12 17:38 ` Phillip Potter
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=20210611002504.166405-1-phil@philpotter.co.uk \
--to=phil@philpotter.co.uk \
--cc=Larry.Finger@lwfinger.net \
--cc=bkkarthik@pesu.pes.edu \
--cc=dan.carpenter@oracle.com \
--cc=gregkh@linuxfoundation.org \
--cc=gustavoars@kernel.org \
--cc=kaixuxia@tencent.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=liushixin2@huawei.com \
--cc=martin@kaiser.cx \
--cc=straube.linux@gmail.com \
--cc=unixbhaskar@gmail.com \
/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.