From: Jonathan Liu <net147@gmail.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH] connman: upgrade to 1.22
Date: Mon, 24 Mar 2014 11:23:02 +1100 [thread overview]
Message-ID: <1395620582-11671-1-git-send-email-net147@gmail.com> (raw)
Highlights:
- If VPN is split routed and not the default service, then allow
DNS queries also to be sent to VPN DNS server.
- Session API fixes
- Memory leak fixes
- Crash fixes
- NTP kiss-of-death packet support
- Support for full USB gadget networking. Now USB gadget network can
be used without tethering.
Signed-off-by: Jonathan Liu <net147@gmail.com>
---
.../recipes-connectivity/connman/{connman_1.21.bb => connman_1.22.bb} | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
rename meta/recipes-connectivity/connman/{connman_1.21.bb => connman_1.22.bb} (68%)
diff --git a/meta/recipes-connectivity/connman/connman_1.21.bb b/meta/recipes-connectivity/connman/connman_1.22.bb
similarity index 68%
rename from meta/recipes-connectivity/connman/connman_1.21.bb
rename to meta/recipes-connectivity/connman/connman_1.22.bb
index 48ed20e..4bd986f 100644
--- a/meta/recipes-connectivity/connman/connman_1.21.bb
+++ b/meta/recipes-connectivity/connman/connman_1.22.bb
@@ -5,7 +5,7 @@ SRC_URI = "${KERNELORG_MIRROR}/linux/network/${BPN}/${BP}.tar.xz \
file://add_xuser_dbus_permission.patch \
file://connman \
"
-SRC_URI[md5sum] = "483633162b819c8b99fec970f92e311d"
-SRC_URI[sha256sum] = "e80f4e9c639ef016e9c497c122c349dbc9e6dc78a9976f986134739ee208c08a"
+SRC_URI[md5sum] = "4f45ab2035d1028a287d14427ce61774"
+SRC_URI[sha256sum] = "64d9a8ab83c99943514bb64984142fef409177a93c64e1aace84eaf13c7bddde"
RRECOMMENDS_${PN} = "connman-conf"
--
1.9.0
reply other threads:[~2014-03-24 0:17 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1395620582-11671-1-git-send-email-net147@gmail.com \
--to=net147@gmail.com \
--cc=openembedded-core@lists.openembedded.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