From: Denis Kenzior <denkenz@gmail.com>
To: ofono@ofono.org
Subject: Re: [PATCH v4 3/8] gprs: Add 'stk' gprs context type
Date: Wed, 01 Jun 2011 00:30:00 -0500 [thread overview]
Message-ID: <4DE5CE58.8030902@gmail.com> (raw)
In-Reply-To: <1305908781-8322-3-git-send-email-philippe.nunes@linux.intel.com>
[-- Attachment #1: Type: text/plain, Size: 1831 bytes --]
Hi Philippe,
On 05/20/2011 11:26 AM, Philippe Nunes wrote:
> ---
> include/gprs-context.h | 1 +
> src/gprs.c | 7 +++++++
> 2 files changed, 8 insertions(+), 0 deletions(-)
>
Please refer to 'Submitting patches' section in HACKING. We do prefer
these to be two separate patches.
> diff --git a/include/gprs-context.h b/include/gprs-context.h
> index f82fcaa..e7976a1 100644
> --- a/include/gprs-context.h
> +++ b/include/gprs-context.h
> @@ -46,6 +46,7 @@ enum ofono_gprs_context_type {
> OFONO_GPRS_CONTEXT_TYPE_MMS,
> OFONO_GPRS_CONTEXT_TYPE_WAP,
> OFONO_GPRS_CONTEXT_TYPE_IMS,
> + OFONO_GPRS_CONTEXT_TYPE_STK,
> };
>
> struct ofono_gprs_primary_context {
> diff --git a/src/gprs.c b/src/gprs.c
> index deffeb8..9657a3e 100644
> --- a/src/gprs.c
> +++ b/src/gprs.c
> @@ -188,6 +188,8 @@ static const char *gprs_context_default_name(enum ofono_gprs_context_type type)
> return "WAP";
> case OFONO_GPRS_CONTEXT_TYPE_IMS:
> return "IMS";
> + case OFONO_GPRS_CONTEXT_TYPE_STK:
> + return "STK";
> }
>
> return NULL;
> @@ -207,6 +209,8 @@ static const char *gprs_context_type_to_string(
> return "wap";
> case OFONO_GPRS_CONTEXT_TYPE_IMS:
> return "ims";
> + case OFONO_GPRS_CONTEXT_TYPE_STK:
> + return "stk";
> }
>
> return NULL;
> @@ -227,6 +231,9 @@ static gboolean gprs_context_string_to_type(const char *str,
> } else if (g_str_equal(str, "ims")) {
> *out = OFONO_GPRS_CONTEXT_TYPE_IMS;
> return TRUE;
> + } else if (g_str_equal(str, "stk")) {
> + *out = OFONO_GPRS_CONTEXT_TYPE_STK;
> + return TRUE;
> }
>
> return FALSE;
I don't really see the point of these changes though. We do not want to
expose STK contexts over D-Bus, so none of these are going to be used.
Regards,
-Denis
next prev parent reply other threads:[~2011-06-01 5:30 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-20 16:26 [PATCH v4 1/8] stk: Clear 'respond_on_exit' flag after sending the terminal response Philippe Nunes
2011-05-20 16:26 ` [PATCH v4 2/8] stk: Introduce BIP command handlers Philippe Nunes
2011-06-02 0:28 ` Denis Kenzior
2011-06-10 14:03 ` Philippe Nunes
2011-06-08 8:01 ` Denis Kenzior
2011-05-20 16:26 ` [PATCH v4 3/8] gprs: Add 'stk' gprs context type Philippe Nunes
2011-06-01 5:30 ` Denis Kenzior [this message]
2011-05-20 16:26 ` [PATCH v4 4/8] gprs: Add private APIs for adding/activating/removing hidden PDP contexts Philippe Nunes
2011-06-01 6:18 ` Denis Kenzior
2011-06-10 9:44 ` Philippe Nunes
2011-06-08 7:46 ` Denis Kenzior
2011-05-20 16:26 ` [PATCH v4 5/8] stk: Use Gprs private APIs to handle the Open channel/Close Channel Philippe Nunes
2011-05-20 16:26 ` [PATCH v4 6/8] gprs: Add a host route for STK context type Philippe Nunes
2011-06-01 6:26 ` Denis Kenzior
2011-05-20 16:26 ` [PATCH v4 7/8] stk: Add support of the Setup event list proactive command Philippe Nunes
2011-05-20 16:26 ` [PATCH v4 8/8] stk: Add read/write handlers Philippe Nunes
2011-06-01 5:26 ` [PATCH v4 1/8] stk: Clear 'respond_on_exit' flag after sending the terminal response 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=4DE5CE58.8030902@gmail.com \
--to=denkenz@gmail.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