From: Greg KH <gregkh@linuxfoundation.org>
To: Edmundo Carmona Antoranz <eantoranz@gmail.com>
Cc: Marco Cesati <marcocesati@gmail.com>,
Dan Carpenter <dan.carpenter@oracle.com>,
Ross Schmidt <ross.schm.dev@gmail.com>,
fabioaiuto83@gmail.com, linux-staging@lists.linux.dev
Subject: Re: Question about rtl8723bs
Date: Tue, 23 Mar 2021 08:15:35 +0100 [thread overview]
Message-ID: <YFmVlyhaO46b4a07@kroah.com> (raw)
In-Reply-To: <CAOc6etYY0yhsdQv+nM3aPxs9ahaEDd=h+vXAesdi65=SiQZ3eA@mail.gmail.com>
On Mon, Mar 22, 2021 at 08:40:11PM -0600, Edmundo Carmona Antoranz wrote:
> Hi!
>
> I was just trying to correct some compiler warnings coming up when
> building this driver. The one problem that took me into kind of a
> rabbit whole was about having K (in rtw_security.h) set as static. So,
> every time it is included somewhere _and_ K is not being used, the
> compiler is nagging about it. Ok.... easy fix, let's remove the static
> keyword and we should be fine. Then I took a look at _where_ it was
> being used.... well, nowhere.... so, ok, let's get rid of it.... oh,
> here are these macros... are they in use? Actually _they are not_....
> let's remove them also.... (I don't know if you are noticing a pattern
> here) then I noticed that _a lot_ of code has been removed recently
> and so I pulled the big guns and cleaned up the file and started to
> add things back as they were being used in the build process.... in
> the end, around 80 lines are gone (give or take) if working on top of
> next, at least.
>
> Is it a good idea to send a patch with all of these things removed or
> they might be coming back later and so they should be kept?
No need to keep anything that is not being used.
If it is needed, it can always be brought back at a later time.
thanks,
greg k-h
next prev parent reply other threads:[~2021-03-23 7:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-23 2:40 Question about rtl8723bs Edmundo Carmona Antoranz
2021-03-23 7:15 ` Greg KH [this message]
2021-03-23 7:28 ` Dan Carpenter
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=YFmVlyhaO46b4a07@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=dan.carpenter@oracle.com \
--cc=eantoranz@gmail.com \
--cc=fabioaiuto83@gmail.com \
--cc=linux-staging@lists.linux.dev \
--cc=marcocesati@gmail.com \
--cc=ross.schm.dev@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