From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] cryptsetup: bump to version 1.6.6
Date: Wed, 29 Oct 2014 21:42:46 +0100 [thread overview]
Message-ID: <20141029214246.70bdcca6@free-electrons.com> (raw)
In-Reply-To: <1414598495-31088-2-git-send-email-gustavo@zacarias.com.ar>
Dear Gustavo Zacarias,
On Wed, 29 Oct 2014 13:01:35 -0300, Gustavo Zacarias wrote:
> Drop upstream patch, add hash file, switch to kernel.org mirror.
>
> Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar>
> ---
> ...ryptsetup-0002-mkdir.patch => 0001-mkdir.patch} | 0
> ...p-0001-link-against-lrt-for-clock_gettime.patch | 33 ----------------------
> package/cryptsetup/cryptsetup.hash | 2 ++
> package/cryptsetup/cryptsetup.mk | 7 +++--
> 4 files changed, 6 insertions(+), 36 deletions(-)
> rename package/cryptsetup/{cryptsetup-0002-mkdir.patch => 0001-mkdir.patch} (100%)
> delete mode 100644 package/cryptsetup/cryptsetup-0001-link-against-lrt-for-clock_gettime.patch
> create mode 100644 package/cryptsetup/cryptsetup.hash
Applied, thanks. If you have some time, it would be great to push
0001-mkdir.patch upstream, so that we can drop AUTORECONF = YES at some
point in the future.
Thanks a lot:
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-10-29 20:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-29 16:01 [Buildroot] [PATCH 1/2] lvm2: bump to version 2.02.111 Gustavo Zacarias
2014-10-29 16:01 ` [Buildroot] [PATCH 2/2] cryptsetup: bump to version 1.6.6 Gustavo Zacarias
2014-10-29 20:42 ` Thomas Petazzoni [this message]
2014-10-29 20:48 ` Gustavo Zacarias
2014-10-29 20:39 ` [Buildroot] [PATCH 1/2] lvm2: bump to version 2.02.111 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=20141029214246.70bdcca6@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