public inbox for buildroot@busybox.net
 help / color / mirror / Atom feed
From: Quentin Schulz via buildroot <buildroot@buildroot.org>
To: Jimmy Durand Wesolowski <jimmy.wesolowski@mobileye.com>,
	buildroot@buildroot.org
Cc: guenther.harrasser@mobileye.com
Subject: Re: [Buildroot] [PATCH 2025.02.x v2] Package/libopenssl: security bump to version 3.5.4
Date: Mon, 23 Mar 2026 16:50:05 +0100	[thread overview]
Message-ID: <b4ab5d3f-e0e7-4c97-9df6-7cfd4ba3db9a@cherry.de> (raw)
In-Reply-To: <20260319124247.2973165-1-jimmy.wesolowski@mobileye.com>

Hi Jimmy,

Your series is somehow malformed, all patches have v2 instead of v2 x/5. 
Your v1 had it correct so I'm not sure what happened since.

I highly suggest to use b4 (https://b4.docs.kernel.org/en/latest/ and 
https://pypi.org/project/b4/) if you can. Otherwise, I believe you can 
generate the series with
git format-patch --cover-letter -v 2 --subject-prefix "PATCH 2025.02.x" 
-M -s -o outgoing origin/2025.02.x
as hinted by the docs in 22.5.4. Patches for maintenance branches.

On 3/19/26 1:42 PM, Jimmy Durand Wesolowski wrote:
> As indicated by Quentin Schulz <quentin.schulz@cherry.de>, OpenSSL 3.4 is
> EoL at the end of 2026, and thus earlier than the Buildroot LTS 2025.02
> (end of 2027).
> OpenSSL version thus needs to be bumped to 3.5.x, which is currently
> 3.5.4. Note that a new 3.5.5 release is in the making.
> This series brings all the related commits from master to 2025.02.x.
> 

Considering we're using this series in one of our products and that 
before that series we had backported the patches internally and they 
were the same as in this series:

Reviewed-by: Quentin Schulz <quentin.schulz@cherry.de>

Thanks!
Quentin
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  parent reply	other threads:[~2026-03-23 15:50 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-16 16:13 [Buildroot] [PATCH 1/5] package/libopenssl: bump version to 3.5.0 Jimmy Durand Wesolowski via buildroot
2026-03-16 16:13 ` [Buildroot] [PATCH 2/5] package/libopenssl: security bump version to 3.5.1 Jimmy Durand Wesolowski via buildroot
2026-03-16 16:13 ` [Buildroot] [PATCH 3/5] package/libopenssl: bump version to 3.5.2 Jimmy Durand Wesolowski via buildroot
2026-03-16 16:13 ` [Buildroot] [PATCH 4/5] package/libopenssl: bump version to 3.5.3 Jimmy Durand Wesolowski via buildroot
2026-03-16 16:13 ` [Buildroot] [PATCH 5/5] package/libopenssl: security bump to version 3.5.4 Jimmy Durand Wesolowski via buildroot
2026-03-17 15:00 ` [Buildroot] [PATCH 1/5] package/libopenssl: bump version to 3.5.0 Quentin Schulz via buildroot
2026-03-17 15:24   ` Jimmy Wesolowski via buildroot
2026-03-17 15:40     ` Quentin Schulz via buildroot
2026-03-19 12:42 ` [Buildroot] [PATCH 2025.02.x v2] Package/libopenssl: security bump to version 3.5.4 Jimmy Durand Wesolowski via buildroot
2026-03-19 12:42   ` [Buildroot] [PATCH 2025.02.x v2] package/libopenssl: bump version to 3.5.0 Jimmy Durand Wesolowski via buildroot
2026-03-19 12:42   ` [Buildroot] [PATCH 2025.02.x v2] package/libopenssl: security bump version to 3.5.1 Jimmy Durand Wesolowski via buildroot
2026-03-19 12:42   ` [Buildroot] [PATCH 2025.02.x v2] package/libopenssl: bump version to 3.5.2 Jimmy Durand Wesolowski via buildroot
2026-03-19 12:42   ` [Buildroot] [PATCH 2025.02.x v2] package/libopenssl: bump version to 3.5.3 Jimmy Durand Wesolowski via buildroot
2026-03-19 12:42   ` [Buildroot] [PATCH 2025.02.x v2] package/libopenssl: security bump to version 3.5.4 Jimmy Durand Wesolowski via buildroot
2026-03-23 15:50   ` Quentin Schulz via buildroot [this message]
2026-03-25  8:39     ` [Buildroot] [PATCH 2025.02.x v2] Package/libopenssl: " Jimmy Wesolowski via buildroot

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=b4ab5d3f-e0e7-4c97-9df6-7cfd4ba3db9a@cherry.de \
    --to=buildroot@buildroot.org \
    --cc=guenther.harrasser@mobileye.com \
    --cc=jimmy.wesolowski@mobileye.com \
    --cc=quentin.schulz@cherry.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