From: Samuel Ortiz <sameo@linux.intel.com>
To: Axel Lin <axel.lin@ingics.com>
Cc: Lauro Ramos Venancio <lauro.venancio@openbossa.org>,
Aloisio Almeida Jr <aloisio.almeida@openbossa.org>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH] NFC: llcp: Use list_for_each_entry in llcp_accept_poll
Date: Fri, 28 Nov 2014 13:42:23 +0100 [thread overview]
Message-ID: <20141128124223.GF29389@ribalta.mp.intel.com> (raw)
In-Reply-To: <1415269241.17088.1.camel@phoenix>
Hi Axel,
On Thu, Nov 06, 2014 at 06:20:41PM +0800, Axel Lin wrote:
> list_for_each_entry_safe() is necessary if list objects are deleted from
> the list while traversing it. Not the case here, so we can use the base
> list_for_each_entry variant.
>
> Signed-off-by: Axel Lin <axel.lin@ingics.com>
> ---
> net/nfc/llcp_sock.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
Applied to nfc-next, thanks.
Cheers,
Samuel.
prev parent reply other threads:[~2014-11-28 12:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-06 10:20 [PATCH] NFC: llcp: Use list_for_each_entry in llcp_accept_poll Axel Lin
2014-11-28 12:42 ` Samuel Ortiz [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=20141128124223.GF29389@ribalta.mp.intel.com \
--to=sameo@linux.intel.com \
--cc=aloisio.almeida@openbossa.org \
--cc=axel.lin@ingics.com \
--cc=lauro.venancio@openbossa.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 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.