From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-networking][PATCH] wolfssl: updated version from 3.6.6 to 3.8.0
Date: Tue, 5 Jan 2016 17:55:11 +0100 [thread overview]
Message-ID: <20160105165511.GC2574@jama> (raw)
In-Reply-To: <BLU436-SMTP1639BAACC4B25952154FE54D6F30@phx.gbl>
[-- Attachment #1: Type: text/plain, Size: 1223 bytes --]
On Tue, Jan 05, 2016 at 09:28:29AM -0700, LC Mac wrote:
> Version 3.8.0 of wolfSSL includes VxWorks example client/server,
> AESNI use with AES-GCM, Stunnel compatibility, C# wrapper, and more.
No change in SRC_URI checksums? Please test the changes you're sending -
this happens with every wolfssl upgrade.
> Signed-off-by: lchristina26 <leah@wolfssl.com>
> ---
> .../recipes-connectivity/wolfssl/{wolfssl_3.6.6.bb => wolfssl_3.8.0.bb} | 0
> 1 file changed, 0 insertions(+), 0 deletions(-)
> rename meta-networking/recipes-connectivity/wolfssl/{wolfssl_3.6.6.bb => wolfssl_3.8.0.bb} (100%)
>
> diff --git a/meta-networking/recipes-connectivity/wolfssl/wolfssl_3.6.6.bb b/meta-networking/recipes-connectivity/wolfssl/wolfssl_3.8.0.bb
> similarity index 100%
> rename from meta-networking/recipes-connectivity/wolfssl/wolfssl_3.6.6.bb
> rename to meta-networking/recipes-connectivity/wolfssl/wolfssl_3.8.0.bb
> --
> 1.9.1
>
> --
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-devel
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 188 bytes --]
prev parent reply other threads:[~2016-01-05 16:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-05 16:28 [meta-networking][PATCH] wolfssl: updated version from 3.6.6 to 3.8.0 LC Mac
2016-01-05 16:55 ` Martin Jansa [this message]
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=20160105165511.GC2574@jama \
--to=martin.jansa@gmail.com \
--cc=openembedded-devel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.