U-Boot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Quentin Schulz <quentin.schulz@cherry.de>
To: Enric Balletbo i Serra <eballetb@redhat.com>
Cc: Eddie Kovsky <ekovsky@redhat.com>, Tom Rini <trini@konsulko.com>,
	Tobias Olausson <tobias@eub.se>,
	Paul HENRYS <paul.henrys_ext@softathome.com>,
	Simon Glass <sjg@chromium.org>, Jan Stancek <jstancek@redhat.com>,
	a.fatoum@pengutronix.de, mark.kettenis@xs4all.nl,
	Mattijs Korpershoek <mkorpershoek@kernel.org>,
	u-boot@lists.denx.de
Subject: Re: [PATCH v4] Add support for OpenSSL Provider API
Date: Fri, 26 Jun 2026 17:46:27 +0200	[thread overview]
Message-ID: <eacd2ffa-a1bd-484b-bf4e-af14fa6c7aba@cherry.de> (raw)
In-Reply-To: <CALE0LRvobvMnm=P4qqcNjzWPhRjtYLO4sbHP4UHOKLTdUoaryA@mail.gmail.com>

Hi Enric, Eddie,

On 6/17/26 10:19 AM, Enric Balletbo i Serra wrote:
> Hi Quentin,
> 
> On Tue, Jun 16, 2026 at 6:43 PM Quentin Schulz <quentin.schulz@cherry.de> wrote:
>>
>> Hi Enric,
>>
>> Thanks for chiming in.
>>
>> On 6/4/26 8:22 AM, Enric Balletbo i Serra wrote:
>>> Hi Quentin and Eddie,
>>>
>>> On Fri, May 22, 2026 at 4:38 PM Quentin Schulz <quentin.schulz@cherry.de> wrote:
>>>>
>>>> Hi Eddie,
>>>>
>>>> On 5/22/26 12:29 AM, Eddie Kovsky wrote:
>>>>> On 05/12/26, Quentin Schulz wrote:
>>>>>> Hi Eddie,
>>>>>>
>>>>>> On 4/29/26 8:02 PM, Eddie Kovsky wrote:
[...]
>>> Does it makes sense?
>>>
>>
>> Somewhat. I still don't understand the obsession with the Provider API
>> when the issue (as I understand it) is "I cannot compile OpenSSL engine
>> support and I don't need it".
>>
> 
> To clarify the "obsession" point, which I think is an unfortunate
> take, my impression was that this wasn't just about throwing a quick,
> blind hack at a Fedora compiler error. The build failure was simply
> the trigger.
> 

I think "no engine support anymore, so providers must be supported" was 
a shortcut many could have taken. I understand (and really appreciate) 
the intent of trying to improve the situation instead of "just" patching 
a build failure and be done with it (after all, I myself just installed 
openssl-devel-engine when I got the build error instead of putting in 
the work Eddie did).

> Eddie put significant effort into researching the modern OpenSSL 3.x
> API, studying how to phase out legacy, deprecated components, looking
> at the U-Boot's testing infrastructure, and trying to proactively
> modernize U-Boot's backend based on established upstream kernel
> patterns.
> 
> I agree, now, and this is the beauty of discussions, that the kernel
> approach is not enough due to its narrow scope. U-Boot’s edge cases
> make a full API migration heavier than expected. However, trying to
> actively clean up technical debt is a valuable goal, and
> characterizing it as a mere obsession with a build error can be quite
> discouraging for new contributors putting in real work to improve the
> codebase.
> 

I do realize that "obsession" was too strong of a word and I apologize 
to Eddie and you. I appreciate the feedback and will try to do better.

Cheers,
Quentin

  reply	other threads:[~2026-06-26 15:46 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-29 18:02 [PATCH v4] Add support for OpenSSL Provider API Eddie Kovsky
2026-04-30  7:54 ` Mattijs Korpershoek
2026-05-12 10:17 ` Quentin Schulz
2026-05-21 22:29   ` Eddie Kovsky
2026-05-22 14:37     ` Quentin Schulz
2026-06-04  6:22       ` Enric Balletbo i Serra
2026-06-16 16:43         ` Quentin Schulz
2026-06-17  8:19           ` Enric Balletbo i Serra
2026-06-26 15:46             ` Quentin Schulz [this message]
2026-08-04 23:21         ` Eddie Kovsky
2026-05-20 10:28 ` Quentin Schulz
2026-05-21 12:43   ` Quentin Schulz
2026-05-20 11:32 ` Quentin Schulz

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=eacd2ffa-a1bd-484b-bf4e-af14fa6c7aba@cherry.de \
    --to=quentin.schulz@cherry.de \
    --cc=a.fatoum@pengutronix.de \
    --cc=eballetb@redhat.com \
    --cc=ekovsky@redhat.com \
    --cc=jstancek@redhat.com \
    --cc=mark.kettenis@xs4all.nl \
    --cc=mkorpershoek@kernel.org \
    --cc=paul.henrys_ext@softathome.com \
    --cc=sjg@chromium.org \
    --cc=tobias@eub.se \
    --cc=trini@konsulko.com \
    --cc=u-boot@lists.denx.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