From: Martin Jansa <martin.jansa@gmail.com>
To: Joshua Lock <joshuagloe@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 0/9] Proposed changes for fido
Date: Fri, 15 Jan 2016 13:10:53 +0100 [thread overview]
Message-ID: <20160115121053.GB2607@jama> (raw)
In-Reply-To: <cover.1450877679.git.joshua.lock@collabora.co.uk>
[-- Attachment #1: Type: text/plain, Size: 2875 bytes --]
On Wed, Dec 23, 2015 at 01:40:36PM +0000, Joshua Lock wrote:
> From: Joshua Lock <joshua.lock@collabora.co.uk>
>
> Please consider the following fixes, available in the joshuagl/fido-next
> branch of openembedded-core-contrib, for the fido branch.
When is this going to be merged?
> Regards,
>
> Joshua
>
> The following changes since commit 9f339f516ab03d598fae0e536b3a420ea4d8ee1a:
>
> bash: Disable custom memory allocator (2015-11-20 15:46:27 +0000)
>
> are available in the git repository at:
>
> git://git.openembedded.org/openembedded-core-contrib joshuagl/fido-next
> http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=joshuagl/fido-next
>
> Armin Kuster (1):
> libxml2: fix CVE-2015-7942 and CVE-2015-8035
>
> Bhuvanchandra DV (1):
> linux-firmware: rtl8192cx: Add latest available firmware
>
> Martin Jansa (2):
> linux-dtb.inc: drop unused DTB_NAME variable from do_install
> feature-arm-thumb.inc: Fix ARMPKGSFX_THUMB value
>
> Mike Crowe (1):
> allarch: Force TARGET_*FLAGS variable values
>
> Richard Purdie (2):
> layer.conf: Add several allarch dependency exclusions
> layer.conf: Add missing dependency for allarch package
> initramfs-framework
>
> Sona Sarmadi (1):
> bind: CVE-2015-8000
>
> Stefan Müller-Klieser (1):
> gcc-4.9: backport from gcc trunk r212178
>
> meta/classes/allarch.bbclass | 4 +
> meta/conf/layer.conf | 11 ++
> .../conf/machine/include/arm/feature-arm-thumb.inc | 2 +-
> .../bind/bind/CVE-2015-8000.patch | 194 +++++++++++++++++++++
> meta/recipes-connectivity/bind/bind_9.9.5.bb | 1 +
> meta/recipes-core/libxml/libxml2.inc | 2 +
> .../libxml/libxml2/CVE-2015-7942.patch | 55 ++++++
> .../libxml/libxml2/CVE-2015-8035.patch | 41 +++++
> meta/recipes-devtools/gcc/gcc-4.9.inc | 1 +
> ...racking.c-backport-from-gcc-trunk-r212178.patch | 39 +++++
> .../linux-firmware/linux-firmware_git.bb | 4 +-
> meta/recipes-kernel/linux/linux-dtb.inc | 1 -
> 12 files changed, 351 insertions(+), 4 deletions(-)
> create mode 100644 meta/recipes-connectivity/bind/bind/CVE-2015-8000.patch
> create mode 100644 meta/recipes-core/libxml/libxml2/CVE-2015-7942.patch
> create mode 100644 meta/recipes-core/libxml/libxml2/CVE-2015-8035.patch
> create mode 100644 meta/recipes-devtools/gcc/gcc-4.9/0062-gcc-var-tracking.c-backport-from-gcc-trunk-r212178.patch
>
> --
> 2.5.0
> --
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 188 bytes --]
next prev parent reply other threads:[~2016-01-15 12:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-23 13:40 [PATCH 0/9] Proposed changes for fido Joshua Lock
2016-01-15 12:10 ` Martin Jansa [this message]
2016-01-15 13:15 ` Richard Purdie
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=20160115121053.GB2607@jama \
--to=martin.jansa@gmail.com \
--cc=joshuagloe@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 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.