From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Christian Melki <christian.melki@t2data.com>
Subject: Re: [ptxdist] [APPLIED] openssl: Version bump. 1.1.1n -> 1.1.1o
Date: Wed, 25 May 2022 11:45:00 +0200 [thread overview]
Message-ID: <20220525094500.2844458-1-m.olbrich@pengutronix.de> (raw)
In-Reply-To: <20220510115724.2691725-1-christian.melki@t2data.com>
Thanks, applied as 7ec10d3c0b8c92e3033e2f551d6b329602fd73ff.
Michael
[sent from post-receive hook]
On Wed, 25 May 2022 11:45:00 +0200, Christian Melki <christian.melki@t2data.com> wrote:
> Minor bugfixes.
>
> * Move patchset, applies cleanly.
>
> Signed-off-by: Christian Melki <christian.melki@t2data.com>
> Message-Id: <20220510115724.2691725-1-christian.melki@t2data.com>
> Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
>
> diff --git a/patches/openssl-1.1.1n/0001-debian-targets.patch b/patches/openssl-1.1.1o/0001-debian-targets.patch
> similarity index 100%
> rename from patches/openssl-1.1.1n/0001-debian-targets.patch
> rename to patches/openssl-1.1.1o/0001-debian-targets.patch
> diff --git a/patches/openssl-1.1.1n/0002-pic.patch b/patches/openssl-1.1.1o/0002-pic.patch
> similarity index 100%
> rename from patches/openssl-1.1.1n/0002-pic.patch
> rename to patches/openssl-1.1.1o/0002-pic.patch
> diff --git a/patches/openssl-1.1.1n/0003-Set-systemwide-default-settings-for-libssl-users.patch b/patches/openssl-1.1.1o/0003-Set-systemwide-default-settings-for-libssl-users.patch
> similarity index 100%
> rename from patches/openssl-1.1.1n/0003-Set-systemwide-default-settings-for-libssl-users.patch
> rename to patches/openssl-1.1.1o/0003-Set-systemwide-default-settings-for-libssl-users.patch
> diff --git a/patches/openssl-1.1.1n/series b/patches/openssl-1.1.1o/series
> similarity index 100%
> rename from patches/openssl-1.1.1n/series
> rename to patches/openssl-1.1.1o/series
> diff --git a/rules/openssl.make b/rules/openssl.make
> index c5a9dd02204c..bdf5dbca5487 100644
> --- a/rules/openssl.make
> +++ b/rules/openssl.make
> @@ -17,9 +17,9 @@ PACKAGES-$(PTXCONF_OPENSSL) += openssl
> # Paths and names
> #
> OPENSSL_BASE := 1.1.1
> -OPENSSL_BUGFIX := n
> +OPENSSL_BUGFIX := o
> OPENSSL_VERSION := $(OPENSSL_BASE)$(OPENSSL_BUGFIX)
> -OPENSSL_MD5 := 2aad5635f9bb338bc2c6b7d19cbc9676
> +OPENSSL_MD5 := d05e96e200d2ff0aef20c114cb5f17bf
> OPENSSL := openssl-$(OPENSSL_VERSION)
> OPENSSL_SUFFIX := tar.gz
> OPENSSL_URL := \
prev parent reply other threads:[~2022-05-25 9:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-10 11:57 [ptxdist] [PATCH] " Christian Melki
2022-05-25 9:45 ` Michael Olbrich [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=20220525094500.2844458-1-m.olbrich@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=christian.melki@t2data.com \
--cc=ptxdist@pengutronix.de \
/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