From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] libtirpc: bump to version 1.0.1
Date: Sun, 8 Nov 2015 14:37:16 +0100 [thread overview]
Message-ID: <20151108143716.31f5c8cd@free-electrons.com> (raw)
In-Reply-To: <CA+BsyQ7XEwj_dLa=H6Yt+rWQMh3rOvH7Bhr=BfWNNkMmVbfnuw@mail.gmail.com>
Dear Brendan Heading,
On Sun, 8 Nov 2015 13:30:45 +0000, Brendan Heading wrote:
> FYI the new 1.0.1 version of libtirpc contains my patch to remove the
> calls to atomic operations that were causing a lot of autobuild
> failures on SPARC (and probably some other lesser-used arches too).
> Took a bit of negotiation to get the patch into a form they were happy
> to accept, but we got there in the end.
>
> So when the bump to 1.0.1 goes in we can expect this class of
> autobuild issues to go away.
Excellent, thanks a lot for working on this topic!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-11-08 13:37 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-05 8:30 [Buildroot] [PATCH 0/2] bump libtirpc to 1.0.1 Peter Rosin
2015-11-05 8:30 ` [Buildroot] [PATCH 1/2] rpcbind: backport adjustment to changes in libtirpc 1.0.1 Peter Rosin
2015-11-06 8:27 ` Peter Rosin
2015-11-05 8:30 ` [Buildroot] [PATCH 2/2] libtirpc: bump to version 1.0.1 Peter Rosin
2015-11-08 13:30 ` Brendan Heading
2015-11-08 13:37 ` Thomas Petazzoni [this message]
2015-11-15 7:43 ` Peter Rosin
2015-11-16 22:08 ` Thomas Petazzoni
2015-11-24 18:43 ` Thomas Petazzoni
2015-11-24 21:52 ` Peter Rosin
2015-11-24 22:08 ` Thomas Petazzoni
2015-11-24 22:12 ` Peter Rosin
2015-11-25 8:05 ` Thomas Petazzoni
2015-11-05 9:05 ` [Buildroot] [PATCH 0/2] bump libtirpc to 1.0.1 Thomas Petazzoni
2015-11-05 10:44 ` Peter Rosin
2015-11-06 8:06 ` Peter Rosin
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=20151108143716.31f5c8cd@free-electrons.com \
--to=thomas.petazzoni@free-electrons.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