From: Giacinto Cifelli <gciofono@gmail.com>
To: ofono@ofono.org
Subject: [RFC PATCH v6 0/1] lte core: additional properties for the default context
Date: Sat, 13 Oct 2018 09:34:32 +0200 [thread overview]
Message-ID: <20181013073433.26680-1-gciofono@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 569 bytes --]
This is a partial submit, for comments.
Related to v5, I have updated the submit description,
added a comment for the storage (that makes clear that protocol and
authentication method are always saved because of their defaults),
and changed the handling of the SetProperty key, taking it from the
incoming message, as suggested by Denis.
Giacinto Cifelli (1):
lte: protocol and authentication for default ctx
src/lte.c | 241 +++++++++++++++++++++++++++++++++++++++++-------------
1 file changed, 185 insertions(+), 56 deletions(-)
--
2.17.1
next reply other threads:[~2018-10-13 7:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-13 7:34 Giacinto Cifelli [this message]
2018-10-13 7:34 ` [RFC PATCH v6 1/1] lte: protocol and authentication for default ctx Giacinto Cifelli
2018-10-16 19:16 ` Denis Kenzior
2018-10-18 7:50 ` Giacinto Cifelli
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=20181013073433.26680-1-gciofono@gmail.com \
--to=gciofono@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