From: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] staging: rtl8188eu: remove unused variables
Date: Fri, 12 Jun 2015 10:52:30 +0530 [thread overview]
Message-ID: <20150612052230.GB15912@sudip-PC> (raw)
In-Reply-To: <1434028149-4135-2-git-send-email-sudipm.mukherjee@gmail.com>
On Thu, Jun 11, 2015 at 06:39:09PM +0530, Sudip Mukherjee wrote:
> These variables were being set but not used afterwards.
>
<snip>
> --- a/drivers/staging/rtl8188eu/core/rtw_sta_mgt.c
> +++ b/drivers/staging/rtl8188eu/core/rtw_sta_mgt.c
> @@ -147,18 +147,14 @@ inline struct sta_info *rtw_get_stainfo_by_offset(struct sta_priv *stapriv, int
> static void rtw_mfree_all_stainfo(struct sta_priv *pstapriv)
> {
> struct list_head *plist, *phead;
> - struct sta_info *psta = NULL;
> -
>
> spin_lock_bh(&pstapriv->sta_hash_lock);
>
> phead = get_list_head(&pstapriv->free_sta_queue);
> plist = phead->next;
>
> - while (phead != plist) {
> - psta = container_of(plist, struct sta_info, list);
> + while (phead != plist)
> plist = plist->next;
> - }
>
> spin_unlock_bh(&pstapriv->sta_hash_lock);
I am checking my own patch ... :)
looks like this function is not doing anything. its just getting the lock,
traversing the list, unlocking and returning.
I am guessing by the function name that the function was supposed to free
something.
Greg - please drop this series. I will try to find if something can be
freed else I will remove this function.
regards
sudip
prev parent reply other threads:[~2015-06-12 5:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-11 13:09 [PATCH 1/2] staging: rtl8188eu: remove unused enum and CONFIG Sudip Mukherjee
2015-06-11 13:09 ` [PATCH 2/2] staging: rtl8188eu: remove unused variables Sudip Mukherjee
2015-06-12 5:22 ` Sudip Mukherjee [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=20150612052230.GB15912@sudip-PC \
--to=sudipm.mukherjee@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®