From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Khem Raj <raj.khem@gmail.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>,
openembeded-devel <openembedded-devel@lists.openembedded.org>,
Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [RFT] Moving on from eglibc to glibc 2.20
Date: Fri, 29 Aug 2014 13:20:46 +0100 [thread overview]
Message-ID: <1409314846.29296.171.camel@ted> (raw)
In-Reply-To: <CAMKF1spj67i2i_50m=oTUpS3x2J=de0UxGf70zLhn-a7c4M3QA@mail.gmail.com>
On Thu, 2014-08-28 at 18:46 -0700, Khem Raj wrote:
> On Thu, Aug 28, 2014 at 5:41 PM, Khem Raj <raj.khem@gmail.com> wrote:
> > reproduced. will apprise as I have some fix.
>
> OK pushed another patch to the contrib tree that should take care of both
> xf86-input-synaptics xf86-input-vmmouse
Also, meta-fsl-ppc fails:
https://autobuilder.yoctoproject.org/main/builders/nightly-fsl-ppc/builds/17/steps/BuildImages/logs/stdio
with a do_compile glibc failure.
Cheers,
Richard
next prev parent reply other threads:[~2014-08-29 12:20 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-28 6:41 [RFT] Moving on from eglibc to glibc 2.20 Khem Raj
2014-08-28 7:18 ` Richard Purdie
2014-08-28 7:52 ` Khem Raj
2014-08-28 21:35 ` Richard Purdie
2014-08-29 0:40 ` Khem Raj
2014-08-28 22:51 ` Richard Purdie
2014-08-29 0:41 ` Khem Raj
2014-08-29 1:46 ` Khem Raj
2014-08-29 10:39 ` Richard Purdie
2014-08-30 0:01 ` Khem Raj
2014-08-30 2:56 ` Khem Raj
2014-08-29 12:18 ` Richard Purdie
2014-08-29 23:59 ` Khem Raj
2014-08-30 3:01 ` Khem Raj
2014-09-02 22:50 ` Dan McGregor
2014-08-29 12:20 ` Richard Purdie [this message]
2014-08-30 0:00 ` 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=1409314846.29296.171.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=openembedded-devel@lists.openembedded.org \
--cc=raj.khem@gmail.com \
--cc=yocto@yoctoproject.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