From: Andrei Emeltchenko <andrei.emeltchenko.news@gmail.com>
To: Gustavo Padovan <gustavo@padovan.org>
Cc: linux-bluetooth@vger.kernel.org,
Gustavo Padovan <gustavo.padovan@collabora.co.uk>
Subject: Re: [PATCH] Bluetooth: Rename __l2cap_connect() to l2cap_connect()
Date: Fri, 12 Oct 2012 15:04:17 +0300 [thread overview]
Message-ID: <20121012120416.GD28051@aemeltch-MOBL1> (raw)
In-Reply-To: <1350042040-1908-1-git-send-email-gustavo@padovan.org>
Hi Gustavo,
On Fri, Oct 12, 2012 at 07:40:40PM +0800, Gustavo Padovan wrote:
> From: Gustavo Padovan <gustavo.padovan@collabora.co.uk>
>
> Use of "__" usually means we need to call the function with a lock held,
> which is not the case here.
I think it is OK to leave the function as is. We do not have such a strong
convention and we have too many locks anyway.
Best regards
Andrei Emeltchenko
next prev parent reply other threads:[~2012-10-12 12:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-12 11:40 [PATCH] Bluetooth: Rename __l2cap_connect() to l2cap_connect() Gustavo Padovan
2012-10-12 12:04 ` Andrei Emeltchenko [this message]
2012-10-12 23:48 ` Marcel Holtmann
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=20121012120416.GD28051@aemeltch-MOBL1 \
--to=andrei.emeltchenko.news@gmail.com \
--cc=gustavo.padovan@collabora.co.uk \
--cc=gustavo@padovan.org \
--cc=linux-bluetooth@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