From: Andrei Emeltchenko <Andrei.Emeltchenko.news@gmail.com>
To: linux-bluetooth@vger.kernel.org
Subject: [PATCHv2 0/9] Improve logging for Android
Date: Tue, 29 Oct 2013 12:21:49 +0200 [thread overview]
Message-ID: <1383042118-21205-1-git-send-email-Andrei.Emeltchenko.news@gmail.com> (raw)
In-Reply-To: <1382957047-31775-1-git-send-email-Andrei.Emeltchenko.news@gmail.com>
From: Andrei Emeltchenko <andrei.emeltchenko@intel.com>
Changes:
*v2: Added thread-safe helpers for printing properties, bdaddr, etc
after comments that simple printing is not thread-safe. The idea is to
use TLS (thread local storage) like bionic is doing for strerror for
example. More info can be found on manpage for pthread_key_create.
This patch series uses debug functions defined already for haltest and
allows to print very helpful logs on Android target like shown below:
...
hal-bluetooth.c:set_adapter_property() prop: type=BT_PROPERTY_ADAPTER_SCAN_MODE len=4 val=BT_SCAN_MODE_NONE
...
Andrei Emeltchenko (9):
android/haltest: Export print property
android/haltest: Fix compile error making function static
android/haltest: Use pointer as parameter for debug
android/hal: Print full property in debug
android/hal: Add extra logs
android/hal: Print adapter state
android/hal: Print adapter property in callback
android: Add thread-safe helpers
android: Use thread-safe helpers
android/client/if-bt.c | 112 +------------------------------------------
android/client/textconv.c | 115 +++++++++++++++++++++++++++++++++++++++++++++
android/client/textconv.h | 3 ++
android/hal-bluetooth.c | 28 ++++++-----
android/pthread-local.h | 58 +++++++++++++++++++++++
5 files changed, 194 insertions(+), 122 deletions(-)
create mode 100644 android/pthread-local.h
--
1.7.10.4
next prev parent reply other threads:[~2013-10-29 10:21 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-28 10:44 [PATCHv1 0/4] Improve logging for Android Andrei Emeltchenko
2013-10-28 10:44 ` [PATCHv1 1/4] android/haltest: Export print property Andrei Emeltchenko
2013-10-28 10:44 ` [PATCHv1 2/4] android/haltest: Use pointer as parameter for debug Andrei Emeltchenko
2013-10-28 10:44 ` [PATCHv1 3/4] android/hal: Print full property in debug Andrei Emeltchenko
2013-10-28 10:44 ` [PATCHv1 4/4] android/hal: Add extra logs Andrei Emeltchenko
2013-10-29 10:21 ` Andrei Emeltchenko [this message]
2013-10-29 10:21 ` [PATCHv2 1/9] android/haltest: Export print property Andrei Emeltchenko
2013-10-29 10:21 ` [PATCHv2 2/9] android/haltest: Fix compile error making function static Andrei Emeltchenko
2013-10-29 10:31 ` Andrei Emeltchenko
2013-10-29 10:21 ` [PATCHv2 3/9] android/haltest: Use pointer as parameter for debug Andrei Emeltchenko
2013-10-29 10:21 ` [PATCHv2 4/9] android/hal: Print full property in debug Andrei Emeltchenko
2013-10-29 10:21 ` [PATCHv2 5/9] android/hal: Add extra logs Andrei Emeltchenko
2013-10-29 10:21 ` [PATCHv2 6/9] android/hal: Print adapter state Andrei Emeltchenko
2013-10-29 10:21 ` [PATCHv2 7/9] android/hal: Print adapter property in callback Andrei Emeltchenko
2013-10-29 10:21 ` [PATCHv2 8/9] android: Add thread-safe helpers Andrei Emeltchenko
2013-10-29 10:21 ` [PATCHv2 9/9] android: Use " Andrei Emeltchenko
2013-10-29 11:43 ` [PATCHv2 0/9] Improve logging for Android Jerzy Kasenberg
2013-10-29 12:18 ` Andrei Emeltchenko
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=1383042118-21205-1-git-send-email-Andrei.Emeltchenko.news@gmail.com \
--to=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.