From: Deepak R Varma <drv@mailo.com>
To: outreachy@lists.linux.dev, gregkh@linuxfoundation.org,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: [PATCH v5 0/1] staging: rtl8192u: unused code cleanup
Date: Tue, 8 Nov 2022 23:38:55 +0530 [thread overview]
Message-ID: <cover.1667930291.git.drv@mailo.com> (raw)
Remove unnecessary or unused code.
Changes in v5:
1. Earlier patch send did not work as expected. The emails did not thread
well. Hence resending as v5.
Changes in v4:
1. Resubmit patch set with the remaining only patch. Update patch subject,
version and patch sequence number to avoid confusion.
Suggested by gregkh@linuxfoundation.org.
Changes in v3:
Patch-1:
1. Already accepted and applied to the stating-testing tree. Hence not
included in this patch set now.
Patch-2:
1. The patch caused staging tree build to fail due to EXPORT_SYMBOL
conflict. Fixed the issue caused due to deletion of 2 macros.
Correction and re-submission asked by gregkh@linuxfoundation.org
Changes in v2:
Patch-1:
1. Revise patch log to explain impact of the patch
Suggested by gregkh@linuxfoundation.org
Patch-2:
1. Review other similar macro defines and clean those up as well.
Suggested by gregkh@linuxfoundation.org
2. Revise patch log to explain impact of the patch
Suggested by julia.lawall@inria.fr
Deepak R Varma (1):
staging: rtl8192u: remove redundant macro definitions
.../staging/rtl8192u/ieee80211/ieee80211.h | 61 -------------------
1 file changed, 61 deletions(-)
--
2.34.1
next reply other threads:[~2022-11-08 18:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-08 18:08 Deepak R Varma [this message]
2022-11-08 18:09 ` [PATCH v5 1/1] staging: rtl8192u: remove redundant macro definitions Deepak R Varma
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.1667930291.git.drv@mailo.com \
--to=drv@mailo.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=outreachy@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).