From: Armin Kuster <akuster808@gmail.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/3] Dizzy next Dec 15th V2
Date: Mon, 15 Dec 2014 09:10:34 -0800 [thread overview]
Message-ID: <cover.1418663308.git.akuster808@gmail.com> (raw)
opps, off-by-1 error.
Please consider these changes for Dizzy-next
This is on top of two previous requests:
http://patches.openembedded.org/patch/84363/
http://patches.openembedded.org/patch/84341/
The following changes since commit 618a569d430e88e9a115dcf10f04384f39e28555:
kernel.bbclass: Create modules directory even if there is no modules installed (2014-12-03 11:28:43 -0800)
are available in the git repository at:
http://git.yoctoproject.org/git/poky-contrib akuster/dizzy-next
http://git.yoctoproject.org/cgit.cgi//log/?h=akuster/dizzy-next
Bian Naimeng (2):
cpio: fix bug CVE-2014-9112 for cpio-2.8
cpio: fix bug CVE-2014-9112 for cpio-2.11
Maxin B. John (1):
python: fix ssl import error
.../python/python-2.7-manifest.inc | 2 +-
.../cpio/cpio-2.11/fix-memory-overrun.patch | 220 +++++++++++++++++++++
.../cpio/cpio-2.8/fix-memory-overrun.patch | 217 ++++++++++++++++++++
meta/recipes-extended/cpio/cpio_2.11.bb | 3 +-
meta/recipes-extended/cpio/cpio_2.8.bb | 7 +-
scripts/contrib/python/generate-manifest-2.7.py | 2 +-
6 files changed, 445 insertions(+), 6 deletions(-)
create mode 100644 meta/recipes-extended/cpio/cpio-2.11/fix-memory-overrun.patch
create mode 100644 meta/recipes-extended/cpio/cpio-2.8/fix-memory-overrun.patch
--
1.9.1
next reply other threads:[~2014-12-15 17:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-15 17:10 Armin Kuster [this message]
2014-12-15 17:10 ` [PATCH 1/3] cpio: fix bug CVE-2014-9112 for cpio-2.8 Armin Kuster
2014-12-15 17:10 ` [PATCH 2/3] cpio: fix bug CVE-2014-9112 for cpio-2.11 Armin Kuster
2014-12-15 17:10 ` [PATCH 3/3] python: fix ssl import error Armin Kuster
2014-12-31 10:26 ` Dizzy Merging Richard Purdie
2015-01-03 0:41 ` akuster808
2015-01-06 14:01 ` Paul Eggleton
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.1418663308.git.akuster808@gmail.com \
--to=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 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.