From: Stafford Horne <shorne@gmail.com>
To: newlib@sourceware.org
Cc: Openrisc <openrisc@lists.librecores.org>,
Stefan Wallentowitz <stefan.wallentowitz@posteo.de>,
Stafford Horne <shorne@gmail.com>
Subject: Re: [PATCH 0/3] openrisc: various fixes
Date: Wed, 15 Mar 2017 11:44:00 -0000 [thread overview]
Message-ID: <CAAfxs75jPZN+kPEx2dESjXvw5dJf2peir7jv6xyfRuut=epd=g@mail.gmail.com> (raw)
In-Reply-To: <cover.1486391219.git.shorne@gmail.com>
Hello,
Any comment on this series?
On Mon, Feb 6, 2017 at 11:38 PM, Stafford Horne <shorne@gmail.com> wrote:
> Hello,
>
> These are a few patches that have collected in the openrisc newlib
> repository on github over the last year. Most issues were found
> when running the gdb test suite as I worked on getting that ready
> for upstream.
>
> I am working with Stefan Wallentowitz who has sent openrisc patches
> in the past.
>
> Olof Kindgren (1):
> or1k: Make open reentrant
>
> Stafford Horne (2):
> libgloss: or1k: If available call the init for init_array
> libgloss: Remove duplicate definition of environ
>
> libgloss/or1k/crt0.S | 6 ++++++
> libgloss/or1k/syscalls.c | 5 +----
> 2 files changed, 7 insertions(+), 4 deletions(-)
>
> --
> 2.9.3
>
next prev parent reply other threads:[~2017-03-15 11:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-06 14:38 Stafford Horne
2017-02-06 14:39 ` [PATCH 1/3] or1k: Make open reentrant Stafford Horne
2017-02-06 14:39 ` [PATCH 3/3] libgloss: Remove duplicate definition of environ Stafford Horne
2017-02-06 14:39 ` [PATCH 2/3] libgloss: or1k: If available call the init for init_array Stafford Horne
2017-02-13 8:20 ` [PATCH 0/3] openrisc: various fixes Corinna Vinschen
2017-03-15 11:44 ` Stafford Horne [this message]
2017-03-15 22:10 ` Stafford Horne
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='CAAfxs75jPZN+kPEx2dESjXvw5dJf2peir7jv6xyfRuut=epd=g@mail.gmail.com' \
--to=shorne@gmail.com \
--cc=newlib@sourceware.org \
--cc=openrisc@lists.librecores.org \
--cc=stefan.wallentowitz@posteo.de \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).