All of lore.kernel.org
 help / color / mirror / Atom feed
From: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
To: Wei Yongjun <weiyj.lk@gmail.com>, Jiri Kosina <jikos@kernel.org>,
	Benjamin Tissoires <benjamin.tissoires@redhat.com>
Cc: Wei Yongjun <weiyongjun1@huawei.com>, linux-input@vger.kernel.org
Subject: Re: [PATCH -next] HID: intel-ish-hid: use list_move_tail instead of list_del/list_add_tail
Date: Fri, 26 Aug 2016 12:04:48 -0700	[thread overview]
Message-ID: <1472238288.2694.5.camel@linux.intel.com> (raw)
In-Reply-To: <1471793249-23714-1-git-send-email-weiyj.lk@gmail.com>

On Sun, 2016-08-21 at 15:27 +0000, Wei Yongjun wrote:
> From: Wei Yongjun <weiyongjun1@huawei.com>
> 
> Using list_move_tail() instead of list_del() + list_add_tail().
> 
> Signed-off-by: Wei Yongjun <weiyongjun1@huawei.com>
Acked-by: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>

> ---
>  drivers/hid/intel-ish-hid/ipc/ipc.c | 3 +--
>  1 file changed, 1 insertion(+), 2 deletions(-)
> 
> diff --git a/drivers/hid/intel-ish-hid/ipc/ipc.c b/drivers/hid/intel-
> ish-hid/ipc/ipc.c
> index 851029b..e2517c1 100644
> --- a/drivers/hid/intel-ish-hid/ipc/ipc.c
> +++ b/drivers/hid/intel-ish-hid/ipc/ipc.c
> @@ -448,8 +448,7 @@ static int ish_fw_reset_handler(struct
> ishtp_device *dev)
>  	spin_lock_irqsave(&dev->wr_processing_spinlock, flags);
>  	list_for_each_entry_safe(processing, next,
>  			&dev->wr_processing_list_head.link, link) {
> -		list_del(&processing->link);
> -		list_add_tail(&processing->link, &dev-
> >wr_free_list_head.link);
> +		list_move_tail(&processing->link, &dev-
> >wr_free_list_head.link);
>  	}
>  	spin_unlock_irqrestore(&dev->wr_processing_spinlock, flags);
>  
> 
> 
> 

      reply	other threads:[~2016-08-26 19:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-21 15:27 [PATCH -next] HID: intel-ish-hid: use list_move_tail instead of list_del/list_add_tail Wei Yongjun
2016-08-26 19:04 ` Srinivas Pandruvada [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=1472238288.2694.5.camel@linux.intel.com \
    --to=srinivas.pandruvada@linux.intel.com \
    --cc=benjamin.tissoires@redhat.com \
    --cc=jikos@kernel.org \
    --cc=linux-input@vger.kernel.org \
    --cc=weiyj.lk@gmail.com \
    --cc=weiyongjun1@huawei.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.