From: Arnd Bergmann <arnd@arndb.de>
To: Binoy Jayan <binoy.jayan@linaro.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Aditya Shankar <aditya.shankar@microchip.com>,
Ganesh Krishna <ganesh.krishna@microchip.com>,
linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: wilc1000: Remove unused function wilc_lock_timeout
Date: Thu, 20 Oct 2016 11:17:59 +0200 [thread overview]
Message-ID: <2246433.KuShhtzXUN@wuerfel> (raw)
In-Reply-To: <1476953672-2198-1-git-send-email-binoy.jayan@linaro.org>
On Thursday, October 20, 2016 2:24:32 PM CEST Binoy Jayan wrote:
> Semaphore are going away in the future, so remove the unused function
> wilc_lock_timeout which calls a semaphore api but has no users.
>
> Signed-off-by: Binoy Jayan <binoy.jayan@linaro.org>
> ---
>
> They following is a patch which removes semaphores from wilc1000.
> Its part of a bigger effort to eliminate all semaphores
> from the linux kernel.
Good catch!
> drivers/staging/wilc1000/linux_wlan.c | 11 -----------
> 1 file changed, 11 deletions(-)
>
> diff --git a/drivers/staging/wilc1000/linux_wlan.c b/drivers/staging/wilc1000/linux_wlan.c
> index 6370a5e..470d59f 100644
> --- a/drivers/staging/wilc1000/linux_wlan.c
> +++ b/drivers/staging/wilc1000/linux_wlan.c
> @@ -218,17 +218,6 @@ static void deinit_irq(struct net_device *dev)
> }
> }
>
> -int wilc_lock_timeout(struct wilc *nic, void *vp, u32 timeout)
> -{
> - /* FIXME: replace with mutex_lock or wait_for_completion */
> - int error = -1;
> -
> - if (vp)
> - error = down_timeout(vp,
> - msecs_to_jiffies(timeout));
> - return error;
> -}
You need to remove the prototype from wilc_wfi_netdevice.h
as well. Once you do that, please add
Reviewed-by: Arnd Bergmann <arnd@arndb.de>
prev parent reply other threads:[~2016-10-20 9:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-20 8:54 [PATCH] staging: wilc1000: Remove unused function wilc_lock_timeout Binoy Jayan
2016-10-20 9:17 ` Arnd Bergmann [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=2246433.KuShhtzXUN@wuerfel \
--to=arnd@arndb.de \
--cc=aditya.shankar@microchip.com \
--cc=binoy.jayan@linaro.org \
--cc=ganesh.krishna@microchip.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@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