From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] uclibc: get rid of ARC's uClibc fork
Date: Tue, 27 Oct 2015 22:09:24 +0100 [thread overview]
Message-ID: <87vb9s81dn.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <1445959005-23917-1-git-send-email-abrodkin@synopsys.com> (Alexey Brodkin's message of "Tue, 27 Oct 2015 18:16:45 +0300")
>>>>> "Alexey" == Alexey Brodkin <Alexey.Brodkin@synopsys.com> writes:
> For quite some time all ARC changes have been pushed upstream.
> So both uClibc master branch and uClibc-ng have full ARC support
> including the most recent changes.
> I.e. finally we have reached the point when there's no need in
> Synopsys fork of uClibc on GitHub and it will soon be obsoleted and
> removed at some pint of time.
> Now since vanilla uClibc hasn't seen any releases for many years we cannot
> really use it for ARC. Fortunately there exists uClibc-ng and Waldemar
> cuts releases regularly - that works perfectly fine for us.
> That patch removes all mentions of ARC's uClibc which in turn makes
> uClibc-ng default libc for ARC.
> Cc: Waldemar Brodkorb <wbx@openadk.org>
> Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
> Signed-off-by: Alexey Brodkin <abrodkin@synopsys.com>
Committed, thanks.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2015-10-27 21:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-27 15:16 [Buildroot] [PATCH] uclibc: get rid of ARC's uClibc fork Alexey Brodkin
2015-10-27 19:13 ` Arnout Vandecappelle
2015-10-27 21:57 ` Thomas Petazzoni
2015-10-27 22:28 ` Arnout Vandecappelle
2015-10-27 22:47 ` Peter Korsgaard
2015-10-27 19:52 ` Waldemar Brodkorb
2015-10-27 21:09 ` Peter Korsgaard [this message]
2015-10-27 21:57 ` Thomas Petazzoni
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=87vb9s81dn.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@busybox.net \
/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