From: Pavel Skripkin <paskripkin@gmail.com>
To: Martin Kaiser <martin@kaiser.cx>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Larry Finger <Larry.Finger@lwfinger.net>,
Phillip Potter <phil@philpotter.co.uk>,
Michael Straube <straube.linux@gmail.com>,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/4] staging: r8188eu: remove empty rtw_*scan* macros
Date: Sat, 10 Sep 2022 22:29:05 +0300 [thread overview]
Message-ID: <9df4bb0a-d494-551b-c7b9-cc93853e8620@gmail.com> (raw)
In-Reply-To: <20220910180236.489808-1-martin@kaiser.cx>
Hi Martin,
Martin Kaiser <martin@kaiser.cx> says:
> Remove four rtw_*scan* macros which are empty or constant.
>
> Martin Kaiser (4):
> staging: r8188eu: remove empty rtw_set_scan_deny macro
> staging: r8188eu: remove rtw_set_scan_deny_timer_hdl
> staging: r8188eu: remove rtw_clear_scan_deny
> staging: r8188eu: rtw_is_scan_deny is always false
>
> drivers/staging/r8188eu/core/rtw_ioctl_set.c | 5 -----
> drivers/staging/r8188eu/core/rtw_mlme.c | 5 -----
> drivers/staging/r8188eu/core/rtw_xmit.c | 3 ---
> drivers/staging/r8188eu/include/rtw_mlme.h | 4 ----
> 4 files changed, 17 deletions(-)
>
Acked-by: Pavel Skripkin <paskripkin@gmail.com>
With regards,
Pavel Skripkin
next prev parent reply other threads:[~2022-09-10 19:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-10 18:02 [PATCH 0/4] staging: r8188eu: remove empty rtw_*scan* macros Martin Kaiser
2022-09-10 18:02 ` [PATCH 1/4] staging: r8188eu: remove empty rtw_set_scan_deny macro Martin Kaiser
2022-09-10 18:02 ` [PATCH 2/4] staging: r8188eu: remove rtw_set_scan_deny_timer_hdl Martin Kaiser
2022-09-10 18:02 ` [PATCH 3/4] staging: r8188eu: remove rtw_clear_scan_deny Martin Kaiser
2022-09-10 18:02 ` [PATCH 4/4] staging: r8188eu: rtw_is_scan_deny is always false Martin Kaiser
2022-09-10 19:29 ` Pavel Skripkin [this message]
2022-09-11 0:48 ` [PATCH 0/4] staging: r8188eu: remove empty rtw_*scan* macros 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=9df4bb0a-d494-551b-c7b9-cc93853e8620@gmail.com \
--to=paskripkin@gmail.com \
--cc=Larry.Finger@lwfinger.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=martin@kaiser.cx \
--cc=phil@philpotter.co.uk \
--cc=straube.linux@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox