From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Armin Kuster <akuster808@gmail.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [jethro][PATCH v2] glibc CVE-2015-7547
Date: Thu, 18 Feb 2016 00:00:12 +0000 [thread overview]
Message-ID: <1455753612.28376.72.camel@linuxfoundation.org> (raw)
In-Reply-To: <1455735734-17911-1-git-send-email-akuster808@gmail.com>
On Wed, 2016-02-17 at 11:02 -0800, Armin Kuster wrote:
> V2 includes changes not committed before sending.
>
> This is being submitted to comply to Yocto compatability.
>
> Master is affected but waiting for 2.23 to be merged before sending
> patches.
Thanks for this.
I've queued up the various CVE glibc patches in master-next, they're
testing on the autobuilder now I'll merge these for master tomorrow
assuming no issues.
For jethro, we've just got a build out of QA, I think we'll likely
release, release note the CVE, then push this onto the jethro branch
straight after.
Cheers,
Richard
prev parent reply other threads:[~2016-02-18 0:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-17 19:02 [jethro][PATCH v2] glibc CVE-2015-7547 Armin Kuster
2016-02-17 19:02 ` [jethro][PATCH] glibc: Security fix CVE-2015-7547 Armin Kuster
2016-02-18 0:00 ` Richard Purdie [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=1455753612.28376.72.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=akuster808@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