From: Gustavo Padovan <gustavo@padovan.org>
To: Vinicius Costa Gomes <vinicius.gomes@openbossa.org>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH v3 7/7] Bluetooth: Add type information to the hci_connect() debug statement
Date: Wed, 15 Aug 2012 01:04:39 -0300 [thread overview]
Message-ID: <20120815040439.GA3344@joana> (raw)
In-Reply-To: <1343428380-32705-8-git-send-email-vinicius.gomes@openbossa.org>
Hi Vinicius,
* Vinicius Costa Gomes <vinicius.gomes@openbossa.org> [2012-07-27 19:33:00 -0300]:
> Now that we have a "connect" function for each link type, we should be
> able to indentify which function is going to be called.
>
> Signed-off-by: Vinicius Costa Gomes <vinicius.gomes@openbossa.org>
> ---
> net/bluetooth/hci_conn.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
all 7 patches have been applied to bluetooth-next. Thanks.
Gustavo
prev parent reply other threads:[~2012-08-15 4:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-27 22:32 [PATCH v3 0/7] Bluetooth: Refactoring hci_connect() Vinicius Costa Gomes
2012-07-27 22:32 ` [PATCH v3 1/7] Bluetooth: Remove some functions from being exported Vinicius Costa Gomes
2012-07-27 22:32 ` [PATCH v3 2/7] Bluetooth: Rename LE and ACL connection functions Vinicius Costa Gomes
2012-07-27 22:32 ` [PATCH v3 3/7] Bluetooth: Refactor LE connection into its own function Vinicius Costa Gomes
2012-07-27 22:32 ` [PATCH v3 4/7] Bluetooth: Refactor ACL " Vinicius Costa Gomes
2012-07-27 22:52 ` Anderson Lizardo
2012-07-27 22:55 ` Anderson Lizardo
2012-07-29 0:13 ` Vinicius Costa Gomes
2012-07-29 1:35 ` [PATCH v4 " Vinicius Costa Gomes
2012-07-27 22:32 ` [PATCH v3 5/7] Bluetooth: Refactor SCO " Vinicius Costa Gomes
2012-08-16 7:14 ` Andrei Emeltchenko
2012-07-27 22:32 ` [PATCH v3 6/7] Bluetooth: Simplify a the connection type handling Vinicius Costa Gomes
2012-07-27 22:33 ` [PATCH v3 7/7] Bluetooth: Add type information to the hci_connect() debug statement Vinicius Costa Gomes
2012-08-15 4:04 ` 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=20120815040439.GA3344@joana \
--to=gustavo@padovan.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=vinicius.gomes@openbossa.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).