All of lore.kernel.org
 help / color / mirror / Atom feed
From: Javier Viguera <javier.viguera@digi.com>
To: "openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>
Subject: Re: [daisy][PATCH] eglibc: security fix CVE-2015-7547
Date: Mon, 11 Apr 2016 12:09:10 +0200	[thread overview]
Message-ID: <570B77C6.5070806@digi.com> (raw)
In-Reply-To: <1459935290-3827-1-git-send-email-javier.viguera@digi.com>

Hi all,

According to the Yocto release page:

https://wiki.yoctoproject.org/wiki/Releases

Daisy is now community maintained.

As the "community" does not have push-permissions to the git server, is 
anyone with permission willing to merge this patch?

The patch is a backport of the CVE-2015-7547 vulnerability fix from 
glibc-2.20 to eglibc-2.19.

I can put this patch in our own BSP layer, but I think oe-core is the 
proper place to commit it, and this way it will benefit to other people 
still using Daisy branch.

-- 
Thanks,

Javier Viguera
Software Engineer
Digi International® Spain S.A.U.


  reply	other threads:[~2016-04-11 10:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-06  9:34 [daisy][PATCH] eglibc: security fix CVE-2015-7547 Javier Viguera
2016-04-11 10:09 ` Javier Viguera [this message]
2016-04-11 10:23 ` Khem Raj

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=570B77C6.5070806@digi.com \
    --to=javier.viguera@digi.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.