From: Andre Guedes <andre.guedes@openbossa.org>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH v2 4/4] Bluetooth: Refactor hci_connect_le
Date: Fri, 04 Oct 2013 17:58:04 -0300 [thread overview]
Message-ID: <524F2BDC.7070804@openbossa.org> (raw)
In-Reply-To: <AC94A523-A61F-4089-8BB8-5EFE52C34ACE@holtmann.org>
Hi Marcel,
On 10/04/2013 03:27 AM, Marcel Holtmann wrote:
> Hi Andre,
>
>> This patch does some code refactoring in hci_connect_le() by moving
>> the exception code into if statements and letting the main flow in
>> first level of function scope. It also adds extra comments to improve
>> the code readability.
>>
>> Signed-off-by: Andre Guedes <andre.guedes@openbossa.org>
>> ---
>> net/bluetooth/hci_conn.c | 55 ++++++++++++++++++++++++++++++------------------
>> 1 file changed, 35 insertions(+), 20 deletions(-)
>>
>> diff --git a/net/bluetooth/hci_conn.c b/net/bluetooth/hci_conn.c
>> index cb0e5d7..ff15841 100644
>> --- a/net/bluetooth/hci_conn.c
>> +++ b/net/bluetooth/hci_conn.c
>> @@ -531,34 +531,49 @@ static struct hci_conn *hci_connect_le(struct hci_dev *hdev, bdaddr_t *dst,
>> if (test_bit(HCI_LE_PERIPHERAL, &hdev->flags))
>> return ERR_PTR(-ENOTSUPP);
>>
>> + /* XXX: Some devices send ATT messages as soon as the physical link
>
> no idea what the XXX wants to tell me here.
The XXX: tag is just a convention programmers use to warn other
programmers about some problematic or special condition in the code. It
is used widely in several projects, including the Linux kernel.
I just "grep'ed" and realized we are not used to use XXX: in Bluetooth
subsystem so I'll remove it.
>
>> + * is established. To be able to handle these ATT messages, the user-
>> + * space first establishes the connection and then starts the pairing
>> + * process.
>> + *
>> + * So if a hci_conn object already exists for the following connection
>> + * attempt, we simply update pending_sec_level and auth_type fields
>> + * and return the object found.
>> + */
>> conn = hci_conn_hash_lookup_ba(hdev, LE_LINK, dst);
>> - if (!conn) {
>> - conn = hci_conn_hash_lookup_state(hdev, LE_LINK, BT_CONNECT);
>> - if (conn)
>> - return ERR_PTR(-EBUSY);
>> -
>> - conn = hci_conn_add(hdev, LE_LINK, dst);
>> - if (!conn)
>> - return ERR_PTR(-ENOMEM);
>> + if (conn) {
>> + conn->pending_sec_level = sec_level;
>> + conn->auth_type = auth_type;
>> + goto out;
>> + }
>
> Call such a label "done". I never really liked the out part.
Ok, I'll rename this label.
Regards,
Andre
prev parent reply other threads:[~2013-10-04 20:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-03 21:25 [PATCH v2 0/4] LE connection refactoring and fixes Andre Guedes
2013-10-03 21:25 ` [PATCH v2 1/4] Bluetooth: Rename hci_conn variable in hci_connect_le() Andre Guedes
2013-10-04 6:08 ` Marcel Holtmann
2013-10-03 21:25 ` [PATCH v2 2/4] Bluetooth: Initialize hci_conn fields in hci_connect_le Andre Guedes
2013-10-04 6:09 ` Marcel Holtmann
2013-10-03 21:25 ` [PATCH v2 3/4] Bluetooth: Use HCI request for LE connection Andre Guedes
2013-10-04 6:25 ` Marcel Holtmann
2013-10-04 20:57 ` Andre Guedes
2013-10-03 21:25 ` [PATCH v2 4/4] Bluetooth: Refactor hci_connect_le Andre Guedes
2013-10-04 6:27 ` Marcel Holtmann
2013-10-04 20:58 ` Andre Guedes [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=524F2BDC.7070804@openbossa.org \
--to=andre.guedes@openbossa.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=marcel@holtmann.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