From: Slawomir Bochenski <lkslawek@gmail.com>
To: linux-bluetooth@vger.kernel.org
Cc: Slawomir Bochenski <lkslawek@gmail.com>
Subject: [PATCH obexd v5 2/5] map_ap.h: Remove MAP_AP_INVALID
Date: Thu, 19 Jan 2012 18:01:53 +0100 [thread overview]
Message-ID: <1326992516-2800-3-git-send-email-lkslawek@gmail.com> (raw)
In-Reply-To: <1326992516-2800-1-git-send-email-lkslawek@gmail.com>
Due to the change in MAP AP definitions resolving, there is no need for
guard value.
---
src/map_ap.h | 1 -
1 files changed, 0 insertions(+), 1 deletions(-)
diff --git a/src/map_ap.h b/src/map_ap.h
index c0fb79a..24254af 100644
--- a/src/map_ap.h
+++ b/src/map_ap.h
@@ -51,7 +51,6 @@ enum map_ap_tag {
MAP_AP_STATUSINDICATOR = 0x17, /* uint8_t */
MAP_AP_STATUSVALUE = 0x18, /* uint8_t */
MAP_AP_MSETIME = 0x19, /* char * */
- MAP_AP_INVALID = 0x100,
};
/* Data type representing MAP application parameters. Consider opaque. */
--
1.7.5.1
next prev parent reply other threads:[~2012-01-19 17:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-19 17:01 Decoding of MAP application parameters Slawomir Bochenski
2012-01-19 17:01 ` [PATCH obexd v5 1/5] MAP: Implementation of MAP AP core functions Slawomir Bochenski
2012-01-20 14:54 ` Johan Hedberg
2012-01-19 17:01 ` Slawomir Bochenski [this message]
2012-01-19 17:01 ` [PATCH obexd v5 3/5] map_ap.c: Add implementation for map_ap_set_* Slawomir Bochenski
2012-01-19 17:01 ` [PATCH obexd v5 4/5] map_ap.c: Add implementation for map_ap_decode() Slawomir Bochenski
2012-01-20 12:25 ` [PATCH obexd v5.1 " Slawomir Bochenski
2012-01-19 17:01 ` [PATCH obexd v5 5/5] map_ap.c: Add dumping of map_ap_t after decoding Slawomir Bochenski
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=1326992516-2800-3-git-send-email-lkslawek@gmail.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).