From: SAURAV GIREPUNJE <saurav.girepunje@gmail.com>
To: Fabio Aiuto <fabioaiuto83@gmail.com>
Cc: gregkh@linuxfoundation.org, Larry.Finger@lwfinger.net,
saurav.girepunje@gmail.com, insafonov@gmail.com,
straube.linux@gmail.com, martin@kaiser.cx, will+git@drnd.me,
dan.carpenter@oracle.com, apais@linux.microsoft.com,
yashsri421@gmail.com, marcocesati@gmail.com,
ross.schm.dev@gmail.com, linux-staging@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/4] staging: rtl8188eu: os_dep: Remove unused variable
Date: Sun, 8 Aug 2021 00:30:17 +0530 [thread overview]
Message-ID: <YQ7YQTCW0kwbxuwm@user> (raw)
In-Reply-To: <20210807145042.GC1425@agape.jhs>
On 07 Aug 2021 16:50, Fabio Aiuto wrote:
> Hello Saurav,
>
> On Sat, Aug 07, 2021 at 03:52:29PM +0530, Saurav Girepunje wrote:
> > Remove unused variable data and data_len from mon_recv_decrypted() in mon.c
> >
> > Signed-off-by: Saurav Girepunje <saurav.girepunje@gmail.com>
> > ---
> > drivers/staging/rtl8188eu/os_dep/mon.c | 5 ++---
> > 1 file changed, 2 insertions(+), 3 deletions(-)
> >
> > diff --git a/drivers/staging/rtl8188eu/os_dep/mon.c b/drivers/staging/rtl8188eu/os_dep/mon.c
>
> did you rebase you local tree on current staging-testing?
> rtl8188eu has been deleted... now there's r8188eu.
>
> thank you,
>
> fabio
I had not done. Now I did it.
thanks fabio for pointing this.
saurav
next prev parent reply other threads:[~2021-08-07 19:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-07 10:22 [PATCH 0/4] Remove unused variable Saurav Girepunje
2021-08-07 10:22 ` [PATCH 1/4] staging: rtl8188eu: os_dep: " Saurav Girepunje
2021-08-07 14:50 ` Fabio Aiuto
2021-08-07 19:00 ` SAURAV GIREPUNJE [this message]
2021-08-07 10:22 ` [PATCH 2/4] staging: rtl8188eu :os_dep :os_intfs : remove " Saurav Girepunje
2021-08-07 10:22 ` [PATCH 3/4] staging: rtl8192e: rtl8192e: rtl_core: remove unused global variable Saurav Girepunje
2021-08-07 10:22 ` [PATCH 4/4] staging: rtl8723bs: os_dep: remove unused variable Saurav Girepunje
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=YQ7YQTCW0kwbxuwm@user \
--to=saurav.girepunje@gmail.com \
--cc=Larry.Finger@lwfinger.net \
--cc=apais@linux.microsoft.com \
--cc=dan.carpenter@oracle.com \
--cc=fabioaiuto83@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=insafonov@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=marcocesati@gmail.com \
--cc=martin@kaiser.cx \
--cc=ross.schm.dev@gmail.com \
--cc=straube.linux@gmail.com \
--cc=will+git@drnd.me \
--cc=yashsri421@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;
as well as URLs for NNTP newsgroup(s).