From: Phillip Potter <phil@philpotter.co.uk>
To: gregkh@linuxfoundation.org
Cc: Larry.Finger@lwfinger.net, dan.carpenter@oracle.com,
linux-kernel@vger.kernel.org, linux-staging@lists.linux.dev
Subject: [PATCH 0/9] staging: rtl8188eu: remove DBG_88E_LEVEL and MSG_88E macros
Date: Thu, 24 Jun 2021 00:48:53 +0100 [thread overview]
Message-ID: <20210623234902.7411-1-phil@philpotter.co.uk> (raw)
This patch set removes all callers of the DBG_88E_LEVEL and MSG_88E
macros, then removes the macro definitions themselves. This code does
not follow kernel coding conventions/best practices and it is better
to remove it and ultimately rely upon pre-existing kernel debugging
and logging functionality.
With these macros gone, there is only RT_TRACE to go (and the other
definitions in include/rtw_debug.h) and then the file can be entirely
removed.
Phillip Potter (9):
staging: rtl8188eu: remove all DBG_88E_LEVEL calls from
os_dep/ioctl_linux.c
staging: rtl8188eu: remove all DBG_88E_LEVEL calls from
core/rtw_mlmw_ext.c
staging: rtl8188eu: remove all DBG_88E_LEVEL calls from
core/rtw_ioctl_set.c
staging: rtl8188eu: remove all DBG_88E_LEVEL calls from
core/rtw_pwrctrl.c
staging: rtl8188eu: remove all DBG_88E_LEVEL calls from
core/rtw_xmit.c
staging: rtl8188eu: remove DBG_88E_LEVEL macro from
include/rtw_debug.h
staging: rtl8188eu: remove MSG_88E call from hal/odm.c
staging: rtl8188eu: remove MSG_88E calls from hal/usb_halinit.c
staging: rtl8188eu: remove MSG_88E macro from include/rtw_debug.h
.../staging/rtl8188eu/core/rtw_ioctl_set.c | 5 -----
drivers/staging/rtl8188eu/core/rtw_mlme_ext.c | 21 -------------------
drivers/staging/rtl8188eu/core/rtw_pwrctrl.c | 9 +-------
drivers/staging/rtl8188eu/core/rtw_xmit.c | 2 --
drivers/staging/rtl8188eu/hal/odm.c | 1 -
drivers/staging/rtl8188eu/hal/usb_halinit.c | 7 -------
drivers/staging/rtl8188eu/include/rtw_debug.h | 12 -----------
.../staging/rtl8188eu/os_dep/ioctl_linux.c | 2 --
8 files changed, 1 insertion(+), 58 deletions(-)
--
2.31.1
next reply other threads:[~2021-06-23 23:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-23 23:48 Phillip Potter [this message]
2021-06-23 23:48 ` [PATCH 1/9] staging: rtl8188eu: remove all DBG_88E_LEVEL calls from os_dep/ioctl_linux.c Phillip Potter
2021-06-23 23:48 ` [PATCH 2/9] staging: rtl8188eu: remove all DBG_88E_LEVEL calls from core/rtw_mlmw_ext.c Phillip Potter
2021-06-23 23:48 ` [PATCH 3/9] staging: rtl8188eu: remove all DBG_88E_LEVEL calls from core/rtw_ioctl_set.c Phillip Potter
2021-06-23 23:48 ` [PATCH 4/9] staging: rtl8188eu: remove all DBG_88E_LEVEL calls from core/rtw_pwrctrl.c Phillip Potter
2021-06-23 23:48 ` [PATCH 5/9] staging: rtl8188eu: remove all DBG_88E_LEVEL calls from core/rtw_xmit.c Phillip Potter
2021-06-23 23:48 ` [PATCH 6/9] staging: rtl8188eu: remove DBG_88E_LEVEL macro from include/rtw_debug.h Phillip Potter
2021-06-23 23:49 ` [PATCH 7/9] staging: rtl8188eu: remove MSG_88E call from hal/odm.c Phillip Potter
2021-06-23 23:49 ` [PATCH 8/9] staging: rtl8188eu: remove MSG_88E calls from hal/usb_halinit.c Phillip Potter
2021-06-23 23:49 ` [PATCH 9/9] staging: rtl8188eu: remove MSG_88E macro from include/rtw_debug.h 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=20210623234902.7411-1-phil@philpotter.co.uk \
--to=phil@philpotter.co.uk \
--cc=Larry.Finger@lwfinger.net \
--cc=dan.carpenter@oracle.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;
as well as URLs for NNTP newsgroup(s).