From: Armin Kuster <akuster808@gmail.com>
To: akuster@mvista.com, openembedded-devel@lists.openembedded.org
Subject: [PATCH 0/2] Pyro-next pull request
Date: Mon, 16 Oct 2017 15:10:47 -0700 [thread overview]
Message-ID: <cover.1508191555.git.akuster808@gmail.com> (raw)
cover leter only:
Please merge Pyro-next to Pyro and apply these changes too.
The following changes since commit 3552877d24845689e7d4e7919ff7b372da70dd40:
wireshark: update to 2.2.9 (2017-09-18 12:06:38 -0700)
are available in the git repository at:
git://git.openembedded.org/meta-openembedded-contrib akuster/pyro-next
http://cgit.openembedded.org/meta-openembedded-contrib/log/?h=akuster/pyro-next
Mark Hatle (1):
hostapd: fix WPA2 key replay security bug
Philip Balister (1):
sip: update recipe to 4.19.2.
.../hostapd/hostapd/key-replay-cve-multiple.patch | 984 +++++++++++++++++++++
.../recipes-connectivity/hostapd/hostapd_2.6.bb | 1 +
.../sip/{sip_4.19.bb => sip_4.19.2.bb} | 4 +-
3 files changed, 987 insertions(+), 2 deletions(-)
create mode 100644 meta-oe/recipes-connectivity/hostapd/hostapd/key-replay-cve-multiple.patch
rename meta-oe/recipes-devtools/sip/{sip_4.19.bb => sip_4.19.2.bb} (92%)
--
2.7.4
reply other threads:[~2017-10-16 22:10 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=cover.1508191555.git.akuster808@gmail.com \
--to=akuster808@gmail.com \
--cc=akuster@mvista.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox