From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3] package: protobuf/python-protobuf: bump to v3.2.0.
Date: Sat, 22 Apr 2017 15:32:39 +0200 [thread overview]
Message-ID: <20170422153239.2c0fc6a2@free-electrons.com> (raw)
In-Reply-To: <20170421160637.6206-1-mrugiero@gmail.com>
Hello,
On Fri, 21 Apr 2017 13:06:37 -0300, mrugiero at gmail.com wrote:
> From: "Mario J. Rugiero" <mrugiero@gmail.com>
>
> Both packages are coupled, so both were bumped and build-tested.
> The atomics' support patch is no longer needed, and neither is
> the autoreconf option, and SPARC64 is no longer broken.
> To make sure of this, one config of each of the following archs
> was tested (base defconfig in parens):
> PowerPC (qemu_ppc_g3beige_defconfig)
> SPARC (qemu_sparc_ss10_defconfig)
> SPARC64 (qemu_sparc64_sun4u_defconfig)
>
> Signed-off-by: Mario J. Rugiero <mrugiero@gmail.com>
> ---
> ...configure.ac-check-if-libatomic-is-needed.patch | 34 ----------------------
> package/protobuf/Config.in | 6 +---
> package/protobuf/protobuf.hash | 2 +-
> package/protobuf/protobuf.mk | 7 ++---
> package/python-protobuf/python-protobuf.hash | 3 +-
> package/python-protobuf/python-protobuf.mk | 2 +-
> 6 files changed, 8 insertions(+), 46 deletions(-)
> delete mode 100644 package/protobuf/0001-configure.ac-check-if-libatomic-is-needed.patch
> mode change 120000 => 100644 package/python-protobuf/python-protobuf.hash
Applied to master, thanks.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-04-22 13:32 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-17 17:22 [Buildroot] [PATCH 1/2] package: protobuf: bump to v3.2.0 mrugiero at gmail.com
2017-04-17 17:22 ` [Buildroot] [PATCH 2/2] new package: grpc mrugiero at gmail.com
2017-04-18 18:26 ` Arnout Vandecappelle
[not found] ` <CAKKQwLQOR_PXG-yLLCn5UxY5dX1wQCs3VNxpkWk_NLSBuY_KCA@mail.gmail.com>
2017-04-19 2:24 ` [Buildroot] Fwd: " Mario Rugiero
2017-04-18 12:08 ` [Buildroot] [PATCH 1/2] package: protobuf: bump to v3.2.0 Arnout Vandecappelle
2017-04-18 12:36 ` Mario Rugiero
2017-04-20 4:41 ` Mario Rugiero
2017-04-20 11:14 ` Arnout Vandecappelle
2017-04-20 14:06 ` [Buildroot] [PATCH v2] package: protobuf/python-protobuf: " mrugiero at gmail.com
2017-04-20 20:25 ` Thomas Petazzoni
2017-04-21 16:06 ` [Buildroot] [PATCH v3] " mrugiero at gmail.com
2017-04-22 13:32 ` Thomas Petazzoni [this message]
2017-04-23 11:59 ` Yann E. MORIN
2017-04-23 13:51 ` Rahul Bedarkar
2017-04-24 11:48 ` Mario Rugiero
2017-04-24 14:03 ` Mario Rugiero
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=20170422153239.2c0fc6a2@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