From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "Mats Kärrman" <Mats.Karrman@tritech.se>
Cc: openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] [Dora] eglibc 2.18: powerpc: Fix time related syscalls
Date: Fri, 28 Mar 2014 13:27:41 +0000 [thread overview]
Message-ID: <1396013261.14790.1.camel@ted> (raw)
In-Reply-To: <ED3E0BCACD909541BA94A34C4A164D4C5B3A7CDB@post.tritech.se>
On Fri, 2014-03-28 at 12:56 +0000, Mats Kärrman wrote:
> Concatenated fix of PowerPC time related system calls in eglibc 2.18 taken
> from upstream glibc. See credits in patch header.
>
> The effect is that some time related system calls returns nothing or garbage.
>
> Tested on PowerPC e300c3.
>
> Eglibc 2.17 does not have this issue and the patches are already part of 2.19.
>
> Signed-off-by: Mats Karrman <mats.karrman@tritech.se>
> ---
> .../ppc-fix-time-related-syscalls.patch | 225 ++++++++++++++++++++
> meta/recipes-core/eglibc/eglibc_2.18.bb | 1 +
> 2 files changed, 226 insertions(+)
> create mode 100644 meta/recipes-core/eglibc/eglibc-2.18/ppc-fix-time-related-syscalls.patch
>
> diff --git a/meta/recipes-core/eglibc/eglibc-2.18/ppc-fix-time-related-syscalls.patch b/meta/recipes-core/eglibc/eglibc-2.18/ppc-fix-time-related-syscalls.patch
> new file mode 100644
> index 0000000..fa1072b
> --- /dev/null
> +++ b/meta/recipes-core/eglibc/eglibc-2.18/ppc-fix-time-related-syscalls.patch
> @@ -0,0 +1,225 @@
> +Concatenated fix of PowerPC time related system calls in eglibc 2.18 taken
> +from upstream glibc. Eglibc 2.17 does not have this issue and the patches are
> +already part of 2.19.
> +This compilation includes the following committs:
> +
This needs an "Upstream-Status: Backport" somewhere in there.
Cheers,
Richard
prev parent reply other threads:[~2014-03-28 13:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-28 12:56 [PATCH] [Dora] eglibc 2.18: powerpc: Fix time related syscalls Mats Kärrman
2014-03-28 13:27 ` 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=1396013261.14790.1.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=Mats.Karrman@tritech.se \
--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.