From: Gustavo Padovan <gustavo@padovan.org>
To: Andrei Emeltchenko <Andrei.Emeltchenko.news@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [RFC] Bluetooth: Improve debugging messages for hci_conn
Date: Sat, 30 Jun 2012 11:42:10 -0300 [thread overview]
Message-ID: <20120630144210.GA1920@joana> (raw)
In-Reply-To: <1339750229-10370-1-git-send-email-Andrei.Emeltchenko.news@gmail.com>
Hi Andrei,
* Andrei Emeltchenko <Andrei.Emeltchenko.news@gmail.com> [2012-06-15 11:50:28 +0300]:
> From: Andrei Emeltchenko <andrei.emeltchenko@intel.com>
>
> Improve debugging of hci_conn objects by: adding print to hci_conn
> refcounting, adding object spcifier when missing, change conn to hcon
> since conn is heavily used for l2cap_conn objects and this is misleading.
>
> Signed-off-by: Andrei Emeltchenko <andrei.emeltchenko@intel.com>
> ---
> include/net/bluetooth/hci_core.h | 6 ++++++
> net/bluetooth/hci_conn.c | 44 +++++++++++++++++++-------------------
> 2 files changed, 28 insertions(+), 22 deletions(-)
Patch has been applied to bluetooth-next, thanks.
Gustavo
prev parent reply other threads:[~2012-06-30 14:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-15 8:50 [RFC] Bluetooth: Improve debugging messages for hci_conn Andrei Emeltchenko
2012-06-30 14:42 ` 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=20120630144210.GA1920@joana \
--to=gustavo@padovan.org \
--cc=Andrei.Emeltchenko.news@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).