From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 02/10] package/nut: Add support for openssl 1.1.x
Date: Sun, 27 Jan 2019 22:04:17 +0100 [thread overview]
Message-ID: <87ef8xolri.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20190125160420.10932-2-patrick.havelange@essensium.com> (Patrick Havelange's message of "Fri, 25 Jan 2019 17:04:12 +0100")
>>>>> "Patrick" == Patrick Havelange <patrick.havelange@essensium.com> writes:
> From: Vadim Kochan <vadim4j@gmail.com>
> Signed-off-by: Vadim Kochan <vadim4j@gmail.com>
> Signed-off-by: Patrick Havelange <patrick.havelange@essensium.com>
> ---
> Changes v6:
> - use the actual upstream patch
> - drop unrelated patch
> ---
> ...Add-compatibility-with-openssl-1.1.0.patch | 75 +++++++++++++++++++
> 1 file changed, 75 insertions(+)
> create mode 100644 package/nut/0003-Add-compatibility-with-openssl-1.1.0.patch
> diff --git a/package/nut/0003-Add-compatibility-with-openssl-1.1.0.patch b/package/nut/0003-Add-compatibility-with-openssl-1.1.0.patch
> new file mode 100644
> index 0000000000..65b7f2d6f7
> --- /dev/null
> +++ b/package/nut/0003-Add-compatibility-with-openssl-1.1.0.patch
> @@ -0,0 +1,75 @@
> +From fcbf18c92918ce5e81d0aab62a7aed5c2245ea4d Mon Sep 17 00:00:00 2001
> +From: Eneas U de Queiroz <cote2004-github@yahoo.com>
> +Date: Fri, 1 Jun 2018 11:17:28 -0300
> +Subject: [PATCH 1/2] Add compatibility with openssl 1.1.0
NIT: check-package complains about PATCH n/m:
package/nut/0003-Add-compatibility-with-openssl-1.1.0.patch:4: generate your patches with 'git format-patch -N'
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2019-01-27 21:04 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-25 16:04 [Buildroot] [PATCH 01/10] package/libshout: Add support for openssl 1.1.x Patrick Havelange
2019-01-25 16:04 ` [Buildroot] [PATCH 02/10] package/nut: " Patrick Havelange
2019-01-27 21:02 ` Peter Korsgaard
2019-01-27 21:04 ` Peter Korsgaard [this message]
2019-01-28 16:47 ` Patrick Havelange
2019-01-25 16:04 ` [Buildroot] [PATCH 03/10] package/vboot-utils: " Patrick Havelange
2019-01-27 21:10 ` Peter Korsgaard
2019-01-25 16:04 ` [Buildroot] [PATCH 04/10] package/pound: Fix build with OpenSSL 1.1.x Patrick Havelange
2019-01-25 16:04 ` [Buildroot] [PATCH 05/10] mariadb: use host-openssl from buildroot-system Patrick Havelange
2019-01-25 16:04 ` [Buildroot] [PATCH 06/10] Introduce the variable BR2_TOOLCHAIN_HAS_UCONTEXT Patrick Havelange
2019-01-25 16:04 ` [Buildroot] [PATCH 07/10] package/thrift: bump to 0.12.0, add support for openssl 1.1.x Patrick Havelange
2019-01-25 16:04 ` [Buildroot] [PATCH 08/10] package/rtmpdump: Fix compilation issues with " Patrick Havelange
2019-01-25 16:04 ` [Buildroot] [PATCH 09/10] freeswitch: bump to git master 8f10ae54a18a19fc6ed938e4f662bd218ba54b5e Patrick Havelange
2019-01-25 16:04 ` [Buildroot] [PATCH 10/10] libopenssl: bump version to 1.1.1a Patrick Havelange
2019-01-27 20:43 ` [Buildroot] [PATCH 01/10] package/libshout: Add support for openssl 1.1.x Peter Korsgaard
2019-01-28 16:49 ` Patrick Havelange
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=87ef8xolri.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.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