mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
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. 3.5.2 -> 3.5.3
Date: Mon, 22 Sep 2025 13:04:31 +0200	[thread overview]
Message-ID: <20250922110431.2077997-1-m.olbrich@pengutronix.de> (raw)
In-Reply-To: <20250919183847.682106-1-christian.melki@t2data.com>

Thanks, applied as ec9d7bebd4487e7e05bfcea2c5b23874eca29481.

Michael

[sent from post-receive hook]

On Mon, 22 Sep 2025 13:04:31 +0200, Christian Melki <christian.melki@t2data.com> wrote:
> Minor bugfixes.
> https://github.com/openssl/openssl/releases/tag/openssl-3.5.3
> 
> * Forward patchset. Applies cleanly.
> 
> Signed-off-by: Christian Melki <christian.melki@t2data.com>
> Message-Id: <20250919183847.682106-1-christian.melki@t2data.com>
> Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
> 
> diff --git a/patches/openssl-3.5.2/0001-debian-targets.patch b/patches/openssl-3.5.3/0001-debian-targets.patch
> similarity index 100%
> rename from patches/openssl-3.5.2/0001-debian-targets.patch
> rename to patches/openssl-3.5.3/0001-debian-targets.patch
> diff --git a/patches/openssl-3.5.2/0002-pic.patch b/patches/openssl-3.5.3/0002-pic.patch
> similarity index 100%
> rename from patches/openssl-3.5.2/0002-pic.patch
> rename to patches/openssl-3.5.3/0002-pic.patch
> diff --git a/patches/openssl-3.5.2/0003-Configure-allow-to-enable-ktls-if-target-does-not-st.patch b/patches/openssl-3.5.3/0003-Configure-allow-to-enable-ktls-if-target-does-not-st.patch
> similarity index 100%
> rename from patches/openssl-3.5.2/0003-Configure-allow-to-enable-ktls-if-target-does-not-st.patch
> rename to patches/openssl-3.5.3/0003-Configure-allow-to-enable-ktls-if-target-does-not-st.patch
> diff --git a/patches/openssl-3.5.2/0004-conf-Serialize-allocation-free-of-ssl_names.patch b/patches/openssl-3.5.3/0004-conf-Serialize-allocation-free-of-ssl_names.patch
> similarity index 100%
> rename from patches/openssl-3.5.2/0004-conf-Serialize-allocation-free-of-ssl_names.patch
> rename to patches/openssl-3.5.3/0004-conf-Serialize-allocation-free-of-ssl_names.patch
> diff --git a/patches/openssl-3.5.2/series b/patches/openssl-3.5.3/series
> similarity index 100%
> rename from patches/openssl-3.5.2/series
> rename to patches/openssl-3.5.3/series
> diff --git a/rules/openssl.make b/rules/openssl.make
> index f84c2643ae16..0a46f5048532 100644
> --- a/rules/openssl.make
> +++ b/rules/openssl.make
> @@ -16,8 +16,8 @@ PACKAGES-$(PTXCONF_OPENSSL) += openssl
>  #
>  # Paths and names
>  #
> -OPENSSL_VERSION		:= 3.5.2
> -OPENSSL_MD5		:= 890fc59f86fc21b5e4d1c031a698dbde
> +OPENSSL_VERSION		:= 3.5.3
> +OPENSSL_MD5		:= 0ec20faeb96bbb203c8684cc7fe4432e
>  OPENSSL			:= openssl-$(OPENSSL_VERSION)
>  OPENSSL_SUFFIX		:= tar.gz
>  OPENSSL_URL		:= \



      reply	other threads:[~2025-09-22 11:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-19 18:38 [ptxdist] [PATCH] " Christian Melki
2025-09-22 11:04 ` 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=20250922110431.2077997-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