[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170912091951.noslc3dlncyxonyg@mwanda>
Date: Tue, 12 Sep 2017 12:19:51 +0300
From: Dan Carpenter <dan.carpenter@...cle.com>
To: Srishti Sharma <srishtishar@...il.com>
Cc: gilad@...yossef.com, devel@...verdev.osuosl.org,
gregkh@...uxfoundation.org, driverdev-devel@...uxdriverproject.org,
linux-kernel@...r.kernel.org, outreachy-kernel@...glegroups.com,
linux-crypto@...r.kernel.org
Subject: Re: [PATCH] Staging: ccree: Don't use volatile for monitor_lock
On Mon, Sep 11, 2017 at 09:29:31PM +0530, Srishti Sharma wrote:
> The use of volatile for the variable monitor_lock is unnecessary.
>
> Signed-off-by: Srishti Sharma <srishtishar@...il.com>
> ---
> drivers/staging/ccree/ssi_request_mgr.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/staging/ccree/ssi_request_mgr.c b/drivers/staging/ccree/ssi_request_mgr.c
> index e5c2f92..7d77941 100644
> --- a/drivers/staging/ccree/ssi_request_mgr.c
> +++ b/drivers/staging/ccree/ssi_request_mgr.c
> @@ -49,7 +49,7 @@ struct ssi_request_mgr_handle {
> dma_addr_t dummy_comp_buff_dma;
> struct cc_hw_desc monitor_desc;
>
> - volatile unsigned long monitor_lock;
> + unsigned long monitor_lock;
The variable seems unused. Try deleting it instead.
regards,
dan carpenter
Powered by blists - more mailing lists