From: maximilian attems <max@stro.at>
To: Matthias Klose <doko@ubuntu.com>
Cc: klibc@zytor.com, linuxppc-dev@lists.ozlabs.org,
Paul Mackerras <paulus@samba.org>
Subject: Re: [PATCH] [klibc] ppc64: Fix build failure with stricter as
Date: Thu, 19 May 2011 13:20:20 +0200 [thread overview]
Message-ID: <20110519112019.GC21271@stro.at> (raw)
In-Reply-To: <1305726080-27589-1-git-send-email-max@stro.at>
On Wed, 18 May 2011, maximilian attems wrote:
> From: Matthias Klose <doko@ubuntu.com>
>
> Landed in Ubuntu klibc version 1.5.20-1ubuntu3.
>
>
> Signed-off-by: maximilian attems <max@stro.at>
> ---
> usr/klibc/arch/ppc64/crt0.S | 17 +++++++++--------
> 1 files changed, 9 insertions(+), 8 deletions(-)
>
thank you, merged in klibc git, will be in next 1.5.23.
--
maks
prev parent reply other threads:[~2011-05-19 11:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-18 13:41 [PATCH] [klibc] ppc64: Fix build failure with stricter as maximilian attems
2011-05-19 11:20 ` maximilian attems [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=20110519112019.GC21271@stro.at \
--to=max@stro.at \
--cc=doko@ubuntu.com \
--cc=klibc@zytor.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=paulus@samba.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;
as well as URLs for NNTP newsgroup(s).