From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] cryptodev-linux: bump to version 1.8
Date: Tue, 1 Dec 2015 17:46:50 +0100 [thread overview]
Message-ID: <20151201174650.358ed096@free-electrons.com> (raw)
In-Reply-To: <1448977966-15980-1-git-send-email-gustavo@zacarias.com.ar>
Gustavo, Peter,
On Tue, 1 Dec 2015 10:52:46 -0300, Gustavo Zacarias wrote:
> Patches are upstream so remove them.
Woohoo, I like when we can get rid of patches because they have been
upstreamed.
> Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar>
> ---
> .../0001-fix-compilation-against-linux-3.19.patch | 37 ----------------
> .../0002-Fix-compilation-against-linux-4.3.patch | 50 ----------------------
> package/cryptodev-linux/cryptodev-linux.hash | 2 +-
> package/cryptodev-linux/cryptodev-linux.mk | 2 +-
> 4 files changed, 2 insertions(+), 89 deletions(-)
> delete mode 100644 package/cryptodev-linux/0001-fix-compilation-against-linux-3.19.patch
> delete mode 100644 package/cryptodev-linux/0002-Fix-compilation-against-linux-4.3.patch
Applied to next (soon to be master).
Peter: this might create a conflict when merging back to master. The
0002-Fix-compilation-against-linux-4.3.patch that Gustavo is removing
here has never been added to next, it had only been added to master. So
when I applied this commit to the next branch, it just discarded the
information that this commit removes
0002-Fix-compilation-against-linux-4.3.patch.
However, when you merge next into master, please make sure to re-remove
0002-Fix-compilation-against-linux-4.3.patch. Otherwise, it will fail
to apply after extracting the new version of cryptodev-linux.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-12-01 16:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-01 13:52 [Buildroot] [PATCH] cryptodev-linux: bump to version 1.8 Gustavo Zacarias
2015-12-01 16:46 ` Thomas Petazzoni [this message]
2015-12-01 19:57 ` Arnout Vandecappelle
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=20151201174650.358ed096@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.