From: Adrian Bunk <bunk@stusta.de>
To: Scott Ellis <scott@jumpnowtek.com>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-networking][warrior][PATCH] wireguard: Upgrade 20190123 -> 20190406
Date: Fri, 31 May 2019 00:33:01 +0300 [thread overview]
Message-ID: <20190530213301.GH318@localhost> (raw)
In-Reply-To: <e5067fbe-0d2d-b2c3-8bb4-29024740cf65@jumpnowtek.com>
On Thu, May 30, 2019 at 04:59:56PM -0400, Scott Ellis wrote:
> http://lists.openembedded.org/pipermail/openembedded-devel/2019-May/199619.html
http://lists.openembedded.org/pipermail/openembedded-devel/2019-May/199620.html
cu
Adrian
> On 5/30/2019 9:16 AM, akuster808 wrote:
> >
> >
> > On 5/30/19 2:04 AM, Scott Ellis wrote:
> >> Fixes issues with kernels 5.1 and greater.
> >>
> >> Backport from master fc1b5310b28f70900a8a432048e08ee06ae309d7
> >
> > What is in this update?
> >
> > - armin
> >>
> >> Signed-off-by: Scott Ellis <scott@jumpnowtek.com>
> >> ---
> >> ...eguard-module_0.0.20190123.bb => wireguard-module_0.0.20190406.bb} | 0
> >> ...ireguard-tools_0.0.20190123.bb => wireguard-tools_0.0.20190406.bb} | 0
> >> meta-networking/recipes-kernel/wireguard/wireguard.inc | 4 ++--
> >> 3 files changed, 2 insertions(+), 2 deletions(-)
> >> rename meta-networking/recipes-kernel/wireguard/{wireguard-module_0.0.20190123.bb => wireguard-module_0.0.20190406.bb} (100%)
> >> rename meta-networking/recipes-kernel/wireguard/{wireguard-tools_0.0.20190123.bb => wireguard-tools_0.0.20190406.bb} (100%)
> >>
> >> diff --git a/meta-networking/recipes-kernel/wireguard/wireguard-module_0.0.20190123.bb b/meta-networking/recipes-kernel/wireguard/wireguard-module_0.0.20190406.bb
> >> similarity index 100%
> >> rename from meta-networking/recipes-kernel/wireguard/wireguard-module_0.0.20190123.bb
> >> rename to meta-networking/recipes-kernel/wireguard/wireguard-module_0.0.20190406.bb
> >> diff --git a/meta-networking/recipes-kernel/wireguard/wireguard-tools_0.0.20190123.bb b/meta-networking/recipes-kernel/wireguard/wireguard-tools_0.0.20190406.bb
> >> similarity index 100%
> >> rename from meta-networking/recipes-kernel/wireguard/wireguard-tools_0.0.20190123.bb
> >> rename to meta-networking/recipes-kernel/wireguard/wireguard-tools_0.0.20190406.bb
> >> diff --git a/meta-networking/recipes-kernel/wireguard/wireguard.inc b/meta-networking/recipes-kernel/wireguard/wireguard.inc
> >> index 8314e79..5cf745e 100644
> >> --- a/meta-networking/recipes-kernel/wireguard/wireguard.inc
> >> +++ b/meta-networking/recipes-kernel/wireguard/wireguard.inc
> >> @@ -11,7 +11,7 @@ LICENSE = "GPLv2"
> >> LIC_FILES_CHKSUM = "file://../COPYING;md5=b234ee4d69f5fce4486a80fdaf4a4263"
> >>
> >> SRC_URI = "https://git.zx2c4.com/WireGuard/snapshot/WireGuard-${PV}.tar.xz"
> >> -SRC_URI[md5sum] = "8a0a232f65d5d86dd408efd9ac30bcf9"
> >> -SRC_URI[sha256sum] = "edd13c7631af169e3838621b1a1bff3ef73cf7bc778eec2bd55f7c1089ffdf9b"
> >> +SRC_URI[md5sum] = "c11254fe48695e61c145a7e82756ecba"
> >> +SRC_URI[sha256sum] = "2f06f3adf70b95e74a7736a22dcf6e9ef623b311a15b7d55b5474e57c3d0415b"
> >>
> >> S = "${WORKDIR}/WireGuard-${PV}/src/"
prev parent reply other threads:[~2019-05-30 21:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-30 9:04 [meta-networking][warrior][PATCH] wireguard: Upgrade 20190123 -> 20190406 Scott Ellis
2019-05-30 13:16 ` akuster808
2019-05-30 20:59 ` Scott Ellis
2019-05-30 21:33 ` Adrian Bunk [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=20190530213301.GH318@localhost \
--to=bunk@stusta.de \
--cc=openembedded-devel@lists.openembedded.org \
--cc=scott@jumpnowtek.com \
/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