From: Yang Gu <yang.gu@intel.com>
To: ofono@ofono.org
Subject: [PATCH v2 02/10] Adjust the sequence of comprehension tlv structures
Date: Tue, 30 Mar 2010 15:57:29 +0800 [thread overview]
Message-ID: <1269935857-4234-2-git-send-email-yang.gu@intel.com> (raw)
In-Reply-To: <1269935857-4234-1-git-send-email-yang.gu@intel.com>
[-- Attachment #1: Type: text/plain, Size: 1331 bytes --]
---
src/stkutil.h | 22 +++++++++++-----------
1 files changed, 11 insertions(+), 11 deletions(-)
diff --git a/src/stkutil.h b/src/stkutil.h
index c4b8970..0a9c145 100644
--- a/src/stkutil.h
+++ b/src/stkutil.h
@@ -347,17 +347,6 @@ struct stk_result {
unsigned char *additional;
};
-/* Defined in TS 102.223 Section 8.19 */
-struct stk_location_info {
- char mnc[OFONO_MAX_MNC_LENGTH + 1];
- char mcc[OFONO_MAX_MCC_LENGTH + 1];
- unsigned short lac_tac;
- ofono_bool_t has_ci;
- unsigned short ci;
- ofono_bool_t has_ext_ci;
- unsigned short ext_ci;
-};
-
/* Define the struct of single file in TS102.223 Section 8.18.
* According to TS 11.11 Section 6.2, each file id has two bytes, and the
* maximum Dedicated File level is 2. So the maximum size of file is 8, which
@@ -369,6 +358,17 @@ struct stk_file {
unsigned int len;
};
+/* Defined in TS 102.223 Section 8.19 */
+struct stk_location_info {
+ char mnc[OFONO_MAX_MNC_LENGTH + 1];
+ char mcc[OFONO_MAX_MCC_LENGTH + 1];
+ unsigned short lac_tac;
+ ofono_bool_t has_ci;
+ unsigned short ci;
+ ofono_bool_t has_ext_ci;
+ unsigned short ext_ci;
+};
+
/*
* According to 102.223 Section 8.24 the length of CTLV is 1 byte. This means
* that the maximum size is 127 according to the rules of CTLVs.
--
1.6.3.3
next prev parent reply other threads:[~2010-03-30 7:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-30 7:57 [PATCH v2 01/10] Add parser for items next action indicator objects Yang Gu
2010-03-30 7:57 ` Yang Gu [this message]
2010-03-30 7:57 ` [PATCH v2 03/10] Add parser for event list objects Yang Gu
2010-03-30 7:57 ` [PATCH v2 04/10] Add parser for cause objects Yang Gu
2010-03-30 7:57 ` [PATCH v2 05/10] Add parser for location status objects Yang Gu
2010-03-30 7:57 ` [PATCH v2 06/10] Add parser for transaction identifier objects Yang Gu
2010-03-30 7:57 ` [PATCH v2 07/10] Add parser for call control requested action objects Yang Gu
2010-03-30 7:57 ` [PATCH v2 08/10] Add enum for icon qualifier Yang Gu
2010-03-30 7:57 ` [PATCH v2 09/10] Adjust the sequence of icon identifier structure Yang Gu
2010-03-30 7:57 ` [PATCH v2 10/10] Add parser for item icon identifier list objects Yang Gu
2010-03-30 15:04 ` [PATCH v2 09/10] Adjust the sequence of icon identifier structure Denis Kenzior
2010-03-30 15:28 ` [PATCH v2 01/10] Add parser for items next action indicator objects Denis Kenzior
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=1269935857-4234-2-git-send-email-yang.gu@intel.com \
--to=yang.gu@intel.com \
--cc=ofono@ofono.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