From: Gustavo Padovan <gustavo@padovan.org>
To: Denis Kirjanov <kirjanov@gmail.com>
Cc: davem@davemloft.net, linux-bluetooth@vger.kernel.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH RESEND net-next] bluetooth: hci_core: Replace list_for_each with list_for_each_entry() helper
Date: Wed, 24 Oct 2012 11:22:34 -0200 [thread overview]
Message-ID: <20121024132234.GG13884@joana> (raw)
In-Reply-To: <1350912121-24171-1-git-send-email-kirjanov@gmail.com>
Hi Denis,
* Denis Kirjanov <kirjanov@gmail.com> [2012-10-22 17:22:01 +0400]:
> Replace list_for_each with list_for_each_entry() helper
>
> Signed-off-by: Denis Kirjanov <kirjanov@gmail.com>
> ---
> include/net/bluetooth/hci_core.h | 20 ++++++++------------
> 1 files changed, 8 insertions(+), 12 deletions(-)
Patch has been applied to bluetooth-next. Thanks.
Gustavo
prev parent reply other threads:[~2012-10-24 13:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-22 13:22 [PATCH RESEND net-next] bluetooth: hci_core: Replace list_for_each with list_for_each_entry() helper Denis Kirjanov
2012-10-22 17:00 ` Marcel Holtmann
2012-10-24 13:22 ` Gustavo Padovan [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=20121024132234.GG13884@joana \
--to=gustavo@padovan.org \
--cc=davem@davemloft.net \
--cc=kirjanov@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).