From: Denis Kenzior <denkenz@gmail.com>
To: ofono@ofono.org
Subject: Re: [PATCH_v3 1/4] GAtPPP: Add ACFC option support
Date: Tue, 28 Jun 2011 12:03:51 -0500 [thread overview]
Message-ID: <4E0A0977.8050801@gmail.com> (raw)
In-Reply-To: <1309255427-10308-2-git-send-email-guillaume.zajac@linux.intel.com>
[-- Attachment #1: Type: text/plain, Size: 1752 bytes --]
Hi Guillaume,
> @@ -658,6 +703,11 @@ void g_at_ppp_set_server_info(GAtPPP *ppp, const char *remote,
> ipcp_set_server_info(ppp->ipcp, r, d1, d2);
> }
>
> +void g_at_ppp_set_acfc_enabled(GAtPPP *ppp)
I really do want the signature to be g_at_ppp_set_acfc_enabled(GAtPPP
*ppp, gboolean enabled)
There are cases where we might re-use the PPP object with different
parameters.
> +{
> + lcp_turn_on_acfc(ppp->lcp);
> +}
> +
> static GAtPPP *ppp_init_common(gboolean is_server, guint32 ip)
> {
> GAtPPP *ppp;
<snip>
> @@ -100,13 +101,19 @@ static void lcp_generate_config_options(struct lcp_data *lcp)
> len += 4;
> }
>
> + if (lcp->req_options & REQ_OPTION_ACFC) {
> + lcp->options[len] = ACFC;
> + lcp->options[len + 1] = 2;
> +
> + len += 2;
> + }
> +
> lcp->options_len = len;
> }
>
> static void lcp_reset_config_options(struct lcp_data *lcp)
> {
> /* Using the default ACCM */
> -
Please don't include random whitespace fixes as part of a larger patch,
send these separately. And in this case the empty line is there on
purpose, since the comment does not refer to
lcp_generate_config_options, but to the fact that options by default are
empty.
> lcp_generate_config_options(lcp);
> }
>
> @@ -286,9 +293,15 @@ static enum rcr_result lcp_rcr(struct pppcp_data *pppcp,
> break;
> case MAGIC_NUMBER:
> case PFC:
> - case ACFC:
> /* don't care */
> break;
> + case ACFC:
> + {
> + struct lcp_data *lcp = pppcp_get_data(pppcp);
Please add a newline here
> + if (lcp->req_options & REQ_OPTION_ACFC)
> + ppp_set_xmit_acfc(ppp, TRUE);
And a newline here
> + break;
> + }
> }
> }
>
Regards,
-Denis
next prev parent reply other threads:[~2011-06-28 17:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-28 10:03 [PATCH_v3 0/4] ACFC and PFC options implementation Guillaume Zajac
2011-06-28 10:03 ` [PATCH_v3 1/4] GAtPPP: Add ACFC option support Guillaume Zajac
2011-06-28 17:03 ` Denis Kenzior [this message]
2011-06-29 1:24 ` Marcel Holtmann
2011-06-28 23:29 ` Denis Kenzior
2011-06-29 1:38 ` Marcel Holtmann
2011-06-28 23:40 ` Denis Kenzior
2011-06-28 10:03 ` [PATCH_v3 2/4] GAtPPP: Add PFC " Guillaume Zajac
2011-06-28 10:03 ` [PATCH_v3 3/4] emulator: Activate ACFC and PFC options onto GAtPPP object Guillaume Zajac
2011-06-28 10:03 ` [PATCH_v3 4/4] gsmdial: Activate ACFC and PFC options on " Guillaume Zajac
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=4E0A0977.8050801@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