The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: James Simmons <jsimmons@infradead.org>
To: simran singhal <singhalsimran0@gmail.com>
Cc: Larry.Finger@lwfinger.net, devel@driverdev.osuosl.org,
	florian.c.schilhabel@googlemail.com, gregkh@linuxfoundation.org,
	linux-kernel@vger.kernel.org, oleg.drokin@intel.com,
	outreachy-kernel@googlegroups.com
Subject: Re: [PATCH v5 3/5] staging: lustre: lustre: Remove unnecessary cast on void pointer
Date: Sun, 5 Mar 2017 00:51:33 +0000 (GMT)	[thread overview]
Message-ID: <alpine.LFD.2.20.1703050050140.10898@casper.infradead.org> (raw)
In-Reply-To: <1488641453-22575-4-git-send-email-singhalsimran0@gmail.com>


> The following Coccinelle script was used to detect this:
> @r@
> expression x;
> void* e;
> type T;
> identifier f;
> @@
> (
>   *((T *)e)
> |
>   ((T *)x)[...]
> |
>   ((T*)x)->f
> |
> - (T*)
>   e
> )
> 
> Signed-off-by: simran singhal <singhalsimran0@gmail.com>

Reviewed-by: James Simmons <jsimmons@infradead.org>

> ---
> 
>  v5:
>    -Fixed compilation warnings.
> 
>  drivers/staging/lustre/lustre/llite/range_lock.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/staging/lustre/lustre/llite/range_lock.c b/drivers/staging/lustre/lustre/llite/range_lock.c
> index 14148a0..161391b 100644
> --- a/drivers/staging/lustre/lustre/llite/range_lock.c
> +++ b/drivers/staging/lustre/lustre/llite/range_lock.c
> @@ -174,7 +174,7 @@ void range_unlock(struct range_lock_tree *tree, struct range_lock *lock)
>   */
>  static enum interval_iter range_lock_cb(struct interval_node *node, void *arg)
>  {
> -	struct range_lock *lock = (struct range_lock *)arg;
> +	struct range_lock *lock = arg;
>  	struct range_lock *overlap = node2rangelock(node);
>  
>  	lock->rl_blocking_ranges += overlap->rl_lock_count + 1;
> -- 
> 2.7.4
> 
> _______________________________________________
> devel mailing list
> devel@linuxdriverproject.org
> http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
> 

  reply	other threads:[~2017-03-05  0:51 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-04 15:30 [PATCH v5 0/5] Remove unnecessary cast on void pointer simran singhal
2017-03-04 15:30 ` [PATCH v5 1/5] staging: nvec: " simran singhal
2017-03-04 15:30 ` [PATCH v5 2/5] staging: lustre: " simran singhal
2017-03-05  0:51   ` James Simmons
2017-03-04 15:30 ` [PATCH v5 3/5] staging: lustre: " simran singhal
2017-03-05  0:51   ` James Simmons [this message]
2017-03-04 15:30 ` [PATCH v5 4/5] staging: rts5208: " simran singhal
2017-03-04 15:30 ` [PATCH v5 5/5] staging: rtl8712: " simran singhal
2017-03-04 15:43 ` [Outreachy kernel] [PATCH v5 0/5] " Julia Lawall
2017-03-04 15:52 ` Joe Perches
2017-03-04 16:03   ` SIMRAN SINGHAL

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=alpine.LFD.2.20.1703050050140.10898@casper.infradead.org \
    --to=jsimmons@infradead.org \
    --cc=Larry.Finger@lwfinger.net \
    --cc=devel@driverdev.osuosl.org \
    --cc=florian.c.schilhabel@googlemail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oleg.drokin@intel.com \
    --cc=outreachy-kernel@googlegroups.com \
    --cc=singhalsimran0@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