All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Bernd Kuhls <bernd@kuhls.net>
Cc: Danny Wood <danny@rotronics.co.uk>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/libopenssl: bump version to 3.0.9
Date: Fri, 14 Jul 2023 23:25:18 +0200	[thread overview]
Message-ID: <20230714232518.6ed70c07@windsurf> (raw)
In-Reply-To: <20230714162339.1907504-1-bernd@kuhls.net>

Hello,

On Fri, 14 Jul 2023 18:23:39 +0200
Bernd Kuhls <bernd@kuhls.net> wrote:

> From: Danny Wood <danny@rotronics.co.uk>
> 
> Rebase patches onto new version
> 
> Remove 0005-crypto-perlasm-ppc-xlate.pl-add-linux64v2-flavour.patch,
> 0006-Add-support-for-io_pgetevents_time64-syscall.patch, and
> 0007-Fixup-support-for-io_pgetevents_time64-syscall.patch as these are
> already applied upstream
> 
> Downloaded from
> https://lists.buildroot.org/pipermail/buildroot/2023-June/669230.html
> 
> Signed-off-by: Bernd Kuhls <bernd@kuhls.net>

How much build testing was done with this version bump? I know OpenSSL
3.x breaks a few APIs compared to OpenSSL 1.x.

Could you do a test build with a significant number of packages using
OpenSSL in Buildroot, to assess the damage caused by this version bump,
and provide the defconfig used for this verification?

Thanks a lot!

Thomas
-- 
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2023-07-14 21:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-14 16:23 [Buildroot] [PATCH 1/1] package/libopenssl: bump version to 3.0.9 Bernd Kuhls
2023-07-14 21:25 ` Thomas Petazzoni via buildroot [this message]
2023-07-15 14:39   ` Peter Korsgaard
     [not found]   ` <87fs5pfdd4.fsf__37810.1900381566$1689431990$gmane$org@48ers.dk>
2023-07-15 15:07     ` Bernd Kuhls

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=20230714232518.6ed70c07@windsurf \
    --to=buildroot@buildroot.org \
    --cc=bernd@kuhls.net \
    --cc=danny@rotronics.co.uk \
    --cc=thomas.petazzoni@bootlin.com \
    /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.