From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH/next] package/c-periphery: bump version to 1.1.1
Date: Mon, 22 May 2017 15:39:52 +0200 [thread overview]
Message-ID: <20170522153952.3e88db5b@free-electrons.com> (raw)
In-Reply-To: <20170521214632.22535-1-bernd.kuhls@t-online.de>
Hello,
On Sun, 21 May 2017 23:46:32 +0200, Bernd Kuhls wrote:
> Removed patches applied upstream:
>
> 0001-Add-missing-header-for-musl-compatibility.patch
> https://github.com/vsergeev/c-periphery/commit/27a95527201a368c825aeaf937700c279e13922a
>
> 0002-Fix-build-on-SPARC.patch
> https://github.com/vsergeev/c-periphery/commit/114c715c78ce300a5cd64fb71f32ffd2bce5326c
>
> Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de>
> ---
> ...Add-missing-header-for-musl-compatibility.patch | 32 ----------
> package/c-periphery/0002-Fix-build-on-SPARC.patch | 70 ----------------------
> package/c-periphery/c-periphery.hash | 2 +-
> package/c-periphery/c-periphery.mk | 2 +-
> 4 files changed, 2 insertions(+), 104 deletions(-)
> delete mode 100644 package/c-periphery/0001-Add-missing-header-for-musl-compatibility.patch
> delete mode 100644 package/c-periphery/0002-Fix-build-on-SPARC.patch
Applied to next, thanks.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2017-05-22 13:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-21 21:46 [Buildroot] [PATCH/next] package/c-periphery: bump version to 1.1.1 Bernd Kuhls
2017-05-22 4:53 ` [Buildroot] FriendlyARM Tiny6410 Riko Ho
2017-05-22 13:39 ` Thomas Petazzoni [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=20170522153952.3e88db5b@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