From: lkslawek@gmail.com
To: linux-bluetooth@vger.kernel.org
Cc: Slawomir Bochenski <lkslawek@gmail.com>
Subject: [PATCH obexd v4 4/4] map_ap.c: Add dumping of map_ap_t after decoding
Date: Wed, 18 Jan 2012 20:06:25 +0100 [thread overview]
Message-ID: <4f171845.9c010e0a.7b51.1df7@mx.google.com> (raw)
In-Reply-To: <1326913585-14577-1-git-send-email-y>
From: Slawomir Bochenski <lkslawek@gmail.com>
---
src/map_ap.c | 25 +++++++++++++++++++++++++
1 files changed, 25 insertions(+), 0 deletions(-)
diff --git a/src/map_ap.c b/src/map_ap.c
index 657d86b..168d163 100644
--- a/src/map_ap.c
+++ b/src/map_ap.c
@@ -125,6 +125,29 @@ static int find_ap_def_offset(uint8_t tag)
return -1;
}
+static void ap_entry_dump(gpointer tag, gpointer val, gpointer user_data)
+{
+ struct ap_entry *entry = val;
+ int offset;
+
+ offset = find_ap_def_offset(GPOINTER_TO_INT(tag));
+
+ switch (ap_defs[offset].type) {
+ case APT_UINT8:
+ DBG("%-30s %08x", ap_defs[offset].name, entry->val.u8);
+ break;
+ case APT_UINT16:
+ DBG("%-30s %08x", ap_defs[offset].name, entry->val.u16);
+ break;
+ case APT_UINT32:
+ DBG("%-30s %08x", ap_defs[offset].name, entry->val.u32);
+ break;
+ case APT_STR:
+ DBG("%-30s %s", ap_defs[offset].name, entry->val.str);
+ break;
+ }
+}
+
static void ap_entry_free(gpointer val)
{
struct ap_entry *entry = val;
@@ -239,6 +262,8 @@ map_ap_t *map_ap_decode(const uint8_t *buffer, size_t length)
}
}
+ g_hash_table_foreach(ap, ap_entry_dump, NULL);
+
return ap;
}
--
1.7.5.1
prev parent reply other threads:[~2012-01-18 19:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1326913585-14577-1-git-send-email-y>
2012-01-18 19:06 ` [PATCH obexd v4 2/4] map_ap.c: Add implementation for map_ap_set_* lkslawek
2012-01-18 19:06 ` [PATCH obexd v4 3/4] map_ap.c: Add implementation for map_ap_decode() lkslawek
2012-01-18 19:06 ` lkslawek [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=4f171845.9c010e0a.7b51.1df7@mx.google.com \
--to=lkslawek@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).