From: Greg KH <gregkh@linuxfoundation.org>
To: Michael Straube <straube.linux@gmail.com>
Cc: Larry.Finger@lwfinger.net, phil@philpotter.co.uk,
martin@kaiser.cx, fmdefrancesco@gmail.com,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] staging: r8188eu: remove unused constants from wifi.h
Date: Thu, 2 Sep 2021 11:23:59 +0200 [thread overview]
Message-ID: <YTCYL85eGWP+s2JX@kroah.com> (raw)
In-Reply-To: <YTCYFu6fAi5vs2IE@kroah.com>
On Thu, Sep 02, 2021 at 11:23:34AM +0200, Greg KH wrote:
> On Sun, Aug 29, 2021 at 08:07:16PM +0200, Michael Straube wrote:
> > The constants WLAN_REASON_PWR_CAPABILITY_NOT_VALID and
> > WLAN_REASON_SUPPORTED_CHANNEL_NOT_VALID defined in wifi.h
> > are unused, remove them.
> >
> > Signed-off-by: Michael Straube <straube.linux@gmail.com>
> > ---
> > drivers/staging/r8188eu/include/wifi.h | 2 --
> > 1 file changed, 2 deletions(-)
> >
> > diff --git a/drivers/staging/r8188eu/include/wifi.h b/drivers/staging/r8188eu/include/wifi.h
> > index 0b3fd94cea18..eb07ac9b8943 100644
> > --- a/drivers/staging/r8188eu/include/wifi.h
> > +++ b/drivers/staging/r8188eu/include/wifi.h
> > @@ -126,8 +126,6 @@ enum WIFI_REASON_CODE {
> > #define WLAN_REASON_DISASSOC_STA_HAS_LEFT 8
> > #define WLAN_REASON_STA_REQ_ASSOC_WITHOUT_AUTH 9 */
> > /* IEEE 802.11h */
>
> This comment can now be deleted, right?
Ah, you do it on the follow-in patch, nevermind...
prev parent reply other threads:[~2021-09-02 9:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-29 18:07 [PATCH 1/2] staging: r8188eu: remove unused constants from wifi.h Michael Straube
2021-08-29 18:07 ` [PATCH 2/2] staging: r8188eu: remove commented " Michael Straube
2021-08-30 0:21 ` Phillip Potter
2021-08-30 0:19 ` [PATCH 1/2] staging: r8188eu: remove unused " Phillip Potter
2021-09-02 9:23 ` Greg KH
2021-09-02 9:23 ` Greg KH [this message]
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=YTCYL85eGWP+s2JX@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=Larry.Finger@lwfinger.net \
--cc=fmdefrancesco@gmail.com \
--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