LKML Archive on lore.kernel.org help / color / mirror / Atom feed
From: Phillip Potter <phil@philpotter.co.uk> To: gregkh@linuxfoundation.org Cc: Larry.Finger@lwfinger.net, linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org Subject: [PATCH 0/8] staging: r8188eu: cleanup several warnings Date: Wed, 11 Aug 2021 00:50:39 +0100 [thread overview] Message-ID: <20210810235047.177883-1-phil@philpotter.co.uk> (raw) This series does a lot of cleanup, and came about due to me noticing that the Makefile contains several lines that silence build warnings about unused variables, functions and so on. It accomplishes does three things therefore: (1) Removes the unused functions no longer called by rtw_ioctl, which was deleted in a previous patch (with the exception of the android code, which I will add back in once ndo_siocdevprivate is merged in). (2) Cleanup all build warnings resulting from removing the offending Makefile lines. (3) Remove the offending Makefile lines so that future build warnings can be caught locally before submission as well. Phillip Potter (8): staging: r8188eu: remove unused functions from os_dep/ioctl_linux.c staging: r8188eu: remove unused oid_null_function function staging: r8188eu: remove unused label from recv_indicatepkt_reorder staging: r8188eu: remove rtw_mfree_sta_priv_lock function staging: r8188eu: remove unused variable from rtl8188e_init_dm_priv staging: r8188eu: remove unused variable from rtw_init_drv_sw staging: r8188eu: remove unused variable from rtw_init_recv_timer staging: r8188eu: remove lines from Makefile that silence build warnings drivers/staging/r8188eu/Makefile | 9 - drivers/staging/r8188eu/core/rtw_recv.c | 2 - drivers/staging/r8188eu/core/rtw_sta_mgt.c | 9 - drivers/staging/r8188eu/hal/rtl8188e_dm.c | 1 - drivers/staging/r8188eu/include/rtw_ioctl.h | 6 - drivers/staging/r8188eu/os_dep/ioctl_linux.c | 1538 ++---------------- drivers/staging/r8188eu/os_dep/os_intfs.c | 1 - drivers/staging/r8188eu/os_dep/recv_linux.c | 2 - 8 files changed, 127 insertions(+), 1441 deletions(-) -- 2.31.1
next reply other threads:[~2021-08-10 23:51 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-08-10 23:50 Phillip Potter [this message] 2021-08-10 23:50 ` [PATCH 1/8] staging: r8188eu: remove unused functions from os_dep/ioctl_linux.c Phillip Potter 2021-08-11 7:40 ` Greg KH 2021-08-11 23:29 ` Phillip Potter 2021-08-10 23:50 ` [PATCH 2/8] staging: r8188eu: remove unused oid_null_function function Phillip Potter 2021-08-10 23:50 ` [PATCH 3/8] staging: r8188eu: remove unused label from recv_indicatepkt_reorder Phillip Potter 2021-08-10 23:50 ` [PATCH 4/8] staging: r8188eu: remove rtw_mfree_sta_priv_lock function Phillip Potter 2021-08-10 23:50 ` [PATCH 5/8] staging: r8188eu: remove unused variable from rtl8188e_init_dm_priv Phillip Potter 2021-08-10 23:50 ` [PATCH 6/8] staging: r8188eu: remove unused variable from rtw_init_drv_sw Phillip Potter 2021-08-10 23:50 ` [PATCH 7/8] staging: r8188eu: remove unused variable from rtw_init_recv_timer Phillip Potter 2021-08-10 23:50 ` [PATCH 8/8] staging: r8188eu: remove lines from Makefile that silence build warnings Phillip Potter 2021-08-11 7:40 ` Greg KH 2021-08-11 6:39 ` [PATCH 0/8] staging: r8188eu: cleanup several warnings Michael Straube 2021-08-11 23:30 ` 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=20210810235047.177883-1-phil@philpotter.co.uk \ --to=phil@philpotter.co.uk \ --cc=Larry.Finger@lwfinger.net \ --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: linkBe 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).