From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: <richard.purdie@linuxfoundation.org>
Cc: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/2] linux-yocto: mips build fixes & config updates
Date: Thu, 16 Jul 2015 01:03:04 -0400 [thread overview]
Message-ID: <cover.1437022827.git.bruce.ashfield@windriver.com> (raw)
Richard,
Here are two fixes that I moved up in my queue in front of the 4.1
kernel, and stable updates to other kernels.
This fixes the mips build issues we've been seeing with gcc5.x and
the 4.9.3 update.
There are minor updates to 3.19 as well, that I wanted to get out now,
rather than sit on them.
Next up is updates to 4.1, the libc-headers and removal of older
kernels.
Cheers,
Bruce
The following changes since commit ba07a69f3dc8fb798e372130bf665d059fed9d42:
dpkg: Fix for Fedora22 and new versions of tar (2015-07-13 13:47:28 +0100)
are available in the git repository at:
git://git.pokylinux.org/poky-contrib zedd/kernel
http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel
Bruce Ashfield (2):
linux-yocto/3.14: fix gcc 4.9.4/5.1 build issues, yaffs2 memory leak
linux-yocto/3.19: drm and axxia updates
meta/recipes-kernel/linux/linux-yocto-rt_3.14.bb | 6 +++---
meta/recipes-kernel/linux/linux-yocto-tiny_3.14.bb | 4 ++--
meta/recipes-kernel/linux/linux-yocto-tiny_3.19.bb | 4 ++--
meta/recipes-kernel/linux/linux-yocto_3.14.bb | 18 +++++++++---------
meta/recipes-kernel/linux/linux-yocto_3.19.bb | 18 +++++++++---------
5 files changed, 25 insertions(+), 25 deletions(-)
--
2.1.0
next reply other threads:[~2015-07-16 5:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-16 5:03 Bruce Ashfield [this message]
2015-07-16 5:03 ` [PATCH 1/2] linux-yocto/3.14: fix gcc 4.9.4/5.1 build issues, yaffs2 memory leak Bruce Ashfield
2015-07-16 5:03 ` [PATCH 2/2] linux-yocto/3.19: drm and axxia updates Bruce Ashfield
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.1437022827.git.bruce.ashfield@windriver.com \
--to=bruce.ashfield@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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